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

Goes well beyond the annotations: it discloses billing semantics (never charged if cancelled), the resulting state (reads back as failed with failureCode generation-cancelled), the refusal condition, and a non-obvious transient 404 retry rule. The idempotentHint=true annotation is reinforced by 'retry the cancel, don't stop'.

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?

Front-loaded with the action and its precondition, then layered with failure-mode guidance; nearly every sentence adds a distinct operational fact. It runs long and the 404 artifact note is niche, but it is not 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?

An output schema exists so return values need not be explained, and the description still covers the full lifecycle: eligibility window, billing outcome, failure code, refusal behavior, and recovery paths. Nothing an agent needs to call this correctly 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 100% and the single parameter is already documented as 'Generation ID returned by generate_pins_from_url', which the description restates rather than extends. Baseline 3 applies since the schema carries the parameter semantics.

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 ('stop a Pin generation started by generate_pins_from_url') and ties it to the exact sibling that creates the object. An agent can distinguish it from get_generation_status and delete_post 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?

Gives explicit when-to-use ('while the generation is still queued'), when-not ('after that the credits are committed and the cancel is refused'), and named alternatives for each fallback path (poll get_generation_status, then delete_post on unwanted drafts). This is a complete routing decision tree.

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