prune_tasks

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

With no annotations, the description carries full burden. It discloses the dry-run safety option, but does not explain criteria for pruning, whether removal is permanent, authentication needs, or side effects. Incomplete behavioral disclosure for a destructive tool.

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?

Three sentences, front-loaded with the primary action. Slight redundancy ('redundant or outdated' then 'no longer needed, have become redundant') but overall clear and efficient.

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?

Covers the main action and dry-run option. With an output schema present, return values are handled separately. However, missing details on input prerequisites or pruning criteria leave gaps for full contextual understanding.

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 coverage is 100% with clear parameter descriptions. The description adds no new meaning beyond schemas, merely restating dry-run functionality. Baseline score of 3 is appropriate.

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?

The description clearly states 'Remove redundant or outdated tasks from the project', specifying the verb, resource, and scope. It distinguishes from siblings like 'remove_task' by describing a bulk, analysis-driven cleanup and offering a dry-run mode.

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?

The description implies usage for bulk cleanup and mentions dry-run vs actual removal, but lacks explicit guidance on when to use this tool versus alternatives like 'remove_task' or 'analyze_project_for_tasks'. No when-not or exclusion criteria are provided.

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