Delete a Dare generation

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

Annotations already provide destructiveHint=true and readOnlyHint=false, and the description adds meaningful behavior beyond that: deletion also removes the output, is irreversible, requires confirmation, and has financial consequences ('Does not refund credits'). This strongly helps the agent understand the full impact of the 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?

The description is compact and front-loaded: it states the action and resource first, then delivers critical cautions. Every sentence earns its place with no filler or redundancy.

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?

For a one-parameter, no-output-schema tool, this description is complete. It covers what is deleted, the destructive nature, the need for confirmation, and the credit policy, leaving no critical operational gap.

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 100%, and the only parameter generation_id is already described as 'Generation id to delete.' The tool description adds no additional parameter meaning, which is acceptable because the schema fully covers it.

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 uses a specific verb ('delete') and identifies the exact resource ('a generation and its output from the Dare library'). It clearly distinguishes this from siblings like get, list, and cancel by emphasizing permanence.

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 provides clear usage context: deletion is destructive, irreversible, requires user confirmation, and does not refund credits. It does not explicitly name alternatives such as dare_cancel_generation, but the safety guidance is strong enough for an agent to know when not to invoke it casually.

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