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

The destructiveHint=true annotation already tells the agent this is a destructive operation. The description adds useful context that the target is a previously generated file identified by a generation ResponseId, but it does not discuss irreversibility, permissions, or other side effects beyond what the annotation provides.

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?

Two compact sentences, front-loaded with the action and resource. The parenthetical clarification and API endpoint detail are useful and do not bloat the description.

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 single-parameter delete tool with no output schema and a clear destructive annotation, the description provides enough context to invoke it correctly. It could mention authorization or whether deletion is permanent, but the essential calling information is present.

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?

The schema already documents responseId at 100% coverage, including that it comes from a prior generation response. The description repeats this meaning without adding format, constraints, or examples beyond the schema, so the baseline 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 states a specific verb and resource: 'Delete a previously generated file by its ResponseId.' It also names the underlying API endpoint, making the operation unambiguous and easy to distinguish from sibling generation and conversion tools.

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 explains the required context for use: the file must have been previously generated and the ResponseId must come from a prior generation response. It does not explicitly state exclusions or alternatives, but none are necessary here because deletion is a distinct operation among the siblings.

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