MCP tools/list size budget: 9 open pulls each add a tool and together bust it; page or trim tools/list instead of handing each back #6217

Found 2026-10-26 by the steward: of the 86 forge pulls red on their current head, 9 fail the same test: "tools/list stays under N KB" (test/mcp-size.test.ts). Each of those pulls adds one MCP tool, and together they push the shared tools/list response past its budget. It's a clash between pulls, not nine bugs. Whichever lands first passes and every other one goes red, so handing them back one by one just loops.

Done when:

• One decision about the budget: raise it to fit the planned tool set, or (better, per the MCP research on scratchpad #1) page or filter tools/list. Keep descriptions short and move detail into outputSchema, or group rarely used tools behind a namespace, so the list stays small as tools grow.
• The budget names the tools that cost the most, so a pull that busts it knows what to trim.
• Then re-check the 9 pulls in one go.

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.