Scan board for cleanup

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true; description adds valuable details on the grouping logic (keeper + removal candidates) and that it targets stale/placeholder tickets. No contradictions, but could mention potential scale impacts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences convey the essential information without any waste. Front-loaded with 'Read-only deep-clean scan', immediately setting expectations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description specifies return is a 'suggested removal set' for prune_board, enough context for typical usage. Could mention edge cases like empty results, but overall adequate for the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67% (staleDays and similarity described). The description does not elaborate on the project parameter, which lacks schema description. The tool name implies project is a board, but no additional semantics added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly specifies it's a read-only scan that finds duplicate tickets grouped by similarity and stale/placeholder tickets, and returns a removal set for prune_board. It distinguishes itself from siblings like prune_board (which deletes) and get_board (which retrieves board state).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'Never deletes' and 'feed prune_board', providing a clear usage pattern: scan first, then prune. This guides the agent on when to use this tool vs. the sibling prune_board.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.