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 what gets destroyed and the precise deletion conditions (keep_last=0 deletes all, before_date is strict), but says nothing about irreversibility, required permissions, or whether a confirmation is expected for a destructive bulk operation.

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?

Front-loaded with the action and result, followed by a compact criteria explanation with no filler. The 'Returns the count and ids deleted' line is mild overlap with the existing output schema, but it is a single clause and reads well at a glance.

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?

An output schema exists so return values need not be detailed, and the description covers the prune semantics and criteria exclusivity adequately for a 3-param destructive tool. Remaining gaps are the lack of any permission/irreversibility note, which would matter for a bulk delete.

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 baseline is 3, but the description adds genuine meaning beyond the schema: the two criteria are mutually exclusive (use exactly one) and keep_last=0 has the special meaning of deleting everything. It also clarifies strictness of before_date, which the schema does not convey.

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?

States a specific verb (bulk-prune) and resource (a report's saved outputs), with the 'bulk' scope implicitly distinguishing it from the singular delete_output_tool sibling. An agent can tell it apart from delete_output_tool and save_output_tool without opening any schema.

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 requires 'exactly one criterion' and explains both options (keep_last, before_date), which is real selection guidance. It does not, however, name an alternative tool or state when a caller should prefer delete_output_tool or list_outputs_tool instead, so it stops short of full routing guidance.

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