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

Annotations already declare destructiveHint=true, so the safety profile is known. The description adds meaningful context beyond that: the deletion is permanent and cannot be undone, user confirmation is required, and in app-capable hosts the result renders as an interactive panel. It doesn't detail error or partial-failure behavior, but the added disclosure is substantial.

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 and ID sources are front-loaded, and the destructive/confirm warning follows immediately. The final sentence about the interactive panel is longer but earns its place by preventing duplicated output in capable hosts.

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 two-parameter destructive tool with no output schema, the description covers target scope, ID provenance, irreversibility, confirmation, and host-specific rendering behavior. Nothing essential to 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 compensates well: id comes from list_generations (or list_uploads for type upload), and the type semantics are clarified for both branches. The full enum list lives in the schema, so the description doesn't need to repeat 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 states a specific verb (permanently delete) and resource (one result from the user's library, or an uploaded file), and it distinguishes the two target categories and their ID sources (list_generations vs list_uploads). An agent can tell exactly what this deletes without opening the 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?

It gives clear context: use it for library results (type + id from list_generations) or uploads (type upload, id from list_uploads), and it mandates confirming with the user first. It does not name sibling alternatives (e.g., delete_post, delete_voice_clone), but the scope is unambiguous.

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