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

Annotations declare destructive and non-readOnly, but the description adds substance beyond them: the cascade invalidation of all tickets, the zero cost, the mandatory owner_ticket credential, irreversibility, and a signed deletion receipt return. This is the kind of side-effect and output disclosure annotations cannot carry, and it is consistent with them (idempotentHint=true is not contradicted by permanent deletion).

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?

Five short clauses, front-loaded with the action and effect, then guards (cost, precondition, irreversibility) and finally the return. Every clause carries information; nothing is padding.

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 destructive tool with no output schema, the description covers side effects, cost, credential requirement, irreversibility, and the return artifact — enough to call it safely. The one gap is how the agent acquires a valid owner_ticket, which matters for a mandatory credential.

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 coverage is 100%, but the schema's own description is a tautology ('The owner_ticket.'), so the baseline applies. The description only reconfirms that owner_ticket is required and does not explain what the ticket is or where the agent obtains it, adding little beyond the schema.

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 and resource ('permanently delete an item') plus its cascade effect ('invalidate all its tickets'), so the agent knows exactly what this does and what collateral change it causes. No sibling overlaps the delete role, so differentiation is implicit but unambiguous.

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 the precondition ('Requires the owner_ticket'), the cost ('Free'), and the irreversibility warning ('Cannot be undone') — solid context for deciding to call it. It stops short of naming when to prefer an alternative path, though no sibling offers a competing delete capability.

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