Audit MCP tool set — count, descriptions, consolidation candidates, budget compliance.
Verify the MCP tool surface is within budget and well-described. Dewey's periodic audit.
grep -c '#\[tool(' crates/mcp-server/src/tools/*.rs | awk -F: '{sum+=$2} END {print "Total tools:", sum}'
Budget: 40 max. Current target: ≤ 32.
If over budget:
grep -B1 'async fn ' crates/mcp-server/src/tools/*.rs | grep 'async fn' | sed 's/.*async fn //; s/(.*//' | sortgrep -B5 'async fn ' crates/mcp-server/src/tools/*.rs | grep 'description = "' | awk -F'description = "' '{print length($2)-2, $2}' | sort -rn | head -10
Any line starting with a number > 100 is over budget.
For each tool description, check:
Look for tool pairs where descriptions differ in <3 keywords — those are merge candidates.
Report markdown:
## Tool Audit (YYYY-MM-DD)
**Total tools:** N / 40 ✅
**Descriptions over 100 chars:** 0 ✅
### Tools by file
...
### Consolidation candidates
- tool_a + tool_b — both search-related, could be merged
### Breaking change budget
Next release: patch / minor / major
search(mode="fuzzy", query="#\\[tool(") to see all tool declarations in contextknowledge(action="search", query="tool consolidation") for historical decisions