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

Annotations already declare readOnly=false, idempotent=true, and destructive=true. The description adds genuinely new context beyond those flags: 'Successful images stay available' tells the agent only pending images are affected, and 'owned' signals an ownership requirement — both useful behavioral details not derivable from structured fields.

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 short sentences, zero filler, with the core action front-loaded and the outcome clarification immediately after. Every phrase earns its place.

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 tool with no output schema and full annotation coverage of the safety profile, the description supplies the key behavioral fact (successful images remain) and ownership scope. It is nearly complete, missing only explicit guidance on the pending precondition or error behavior.

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 parameter meaning but offers none beyond the term 'AI image'; it never explains ai_image_id or its format. The schema's regex pattern partially compensates by defining the id structure, so a baseline 3 is appropriate for this simple single-parameter tool.

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 ('Cancel an owned pending AI image'), which cleanly identifies the operation and scopes it to pending, owned images. It does not name any sibling tool for comparison, but the AI-image resource clearly distinguishes it from cancel_batch or cancel_template_message.

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?

The word 'pending' implies the precondition for use, and 'owned' hints at an authorization constraint, but there is no explicit when-to-use, when-not-to-use, or reference to an alternative like retry or get_status. Usage is inferable rather than stated.

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