Prune Outputs Tool

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

With no annotations, the description carries the full behavioral burden. It discloses that outputs are deleted, that keep_last=0 deletes all, and that it returns count and ids, but it does not state whether deletion is irreversible or what permissions are required.

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?

The description is short and front-loaded: purpose and return value first, then criterion semantics. Every sentence adds useful information without repetition.

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?

The schema fully documents parameters, an output schema exists, and the description explains the pruning criteria and return summary. The main remaining gap is behavioral safety context such as irreversibility and permissions, which matters because no annotations are provided.

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%, so the baseline is 3, but the description adds important meaning beyond the schema. It clarifies the exactly-one-criterion constraint and explains the special keep_last=0 case and the strict 'before' behavior of before_date.

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 states a specific verb and resource: bulk-prune a report's saved outputs. The word 'bulk' helps distinguish it from a single-output deletion tool, though it does not explicitly name delete_output_tool as the alternative.

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?

It clearly instructs that exactly one criterion must be given and explains how to choose between keep_last and before_date. It does not explicitly compare this tool with delete_output_tool or list_outputs_tool, but the usage context is clear.

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