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

Annotations already declare destructiveHint=true, so the safety flag is covered, but the description adds real value beyond it: the operation is permanent and cannot be undone, requires user confirmation, and in app-capable hosts renders an interactive panel that should not be echoed back as text. These are non-obvious behavioral traits an agent could not infer from the schema.

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?

Purpose is front-loaded, followed by the irreversibility/confirmation constraint and then the host-rendering guidance. The final sentence is long but every clause is actionable; nothing is redundant.

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 2-parameter, no-output-schema destructive tool, the description covers both operating modes, id sourcing, irreversibility, confirmation, and host-specific output handling. Nothing material for correct invocation is missing.

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 0%, so the description must carry the load. It explains the origin of 'id' (list_generations / list_uploads) and the special meaning of type='upload', which compensates for the highest-value ambiguity, but it does not explain the 14 other enum values or the type/id pairing relationship.

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 (permanently delete) and resource (a generation result or uploaded file), and disambiguates the two modes via the type field. An agent can tell it apart from delete_post and delete_voice_clone 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 routes the agent to the source tools for the id (list_generations for results, list_uploads for the 'upload' type) and mandates confirming with the user first. It does not, however, contrast against the sibling delete_post/delete_voice_clone tools, so the exclusion side is implied rather than stated.

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