Delete Output Tool

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the error case ('raises if no output carries that id') and that the response echoes the deleted object with deleted=True, but for a destructive operation it says nothing about irreversibility, permissions, or whether deletion is soft or hard.

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 short sentences, front-loaded with the action and scope, then return behavior, then id discovery, then the failure case. No filler and nothing buried.

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 the return-value sentence is supplementary rather than required, and the id source and error behavior are covered. The remaining gap is behavioral: nothing tells the agent whether a delete is recoverable, which matters for an irreversible mutation with no annotations.

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?

Only one parameter exists and schema description coverage is 100%, with the schema already noting the id comes from list_outputs_tool. The description repeats that source but adds no new syntax, format, or range meaning, so baseline 3 applies.

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 (delete) and resource (saved report output) with explicit scope ('one ... by id'), which cleanly separates it from the bulk-deleting sibling prune_outputs_tool. It also names list_outputs_tool as the id source, so an agent can distinguish it from the get/save output tools without opening a 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?

Gives clear operational context: ids come from list_outputs_tool, and the tool deletes exactly one output. However it never states when to prefer this over the sibling prune_outputs_tool, nor any prerequisite or exclusion, so the alternative-selection guidance is incomplete.

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