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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds genuine context beyond that: it also destroys stored images, and it requires prior in-chat user confirmation. It does not disclose irreversibility beyond what destructiveHint implies, nor any batch/limit behavior, keeping it below 5.

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 sentences, action front-loaded and the precondition second — no filler. The 'as the platform's Delete' phrase is slightly redundant and costs a small amount of clarity.

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 destructive delete with no output schema and no param docs, the description covers the essentials: what gets removed, that it is irreversible, and the confirmation gate. It omits how to source valid IDs and the 100-item batch ceiling, which are the remaining operational gaps.

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 schema supplies structure only (array of positive ints, 1-100 items) with no semantics. The description alludes to 'which results to delete' but never explains the parameter's format, valid range, or where IDs are obtained; it does not compensate for the coverage gap.

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 (the user's results and their stored images), and clarifies it maps to the platform's own Delete. An agent can distinguish it from read-side siblings like mcp_read_generation_result and sibling mutations like set_generation_result_favorite. The 'as the platform's Delete' clause is slightly awkward but does not obscure the action.

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 an explicit precondition for invocation: 'call it only after the user confirmed in chat which results to delete.' This is exactly the gating guidance a destructive tool needs. It stops short of naming an alternative or where the IDs originate, so not a full 5.

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