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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the operationally important nuances: waiting items are CANCELED with nothing charged, while the item being drawn is allowed to finish. It also discloses the return value (`canceled` count) and how to confirm the result, which annotations cannot convey.

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 verb and scope, then conditional outcomes, return value, and the alternative. Every sentence carries information, though the dense backtick/parenthetical style makes it slightly harder to skim than it could be.

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?

With no output schema, the description still discloses the response (`canceled` count) and a verification path. The only gap is the undocumented character_uuid format, which is minor for a single obvious identifier.

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 0% for the single `character_uuid` parameter and the description never states its expected format or where to obtain it. The name is self-evident and the surrounding narrative implies it scopes to one character, but no explicit compensation for the coverage gap is given.

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 ([write] Stop the production queued with queue_character_assets) and describes exactly what is affected: still-QUEUED pictures are removed, the in-progress PROCESS item finishes. It explicitly distinguishes itself from the sibling cancel_character_image, which handles scene pictures.

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?

Names the upstream tool that created the work (queue_character_assets), names the alternative for a different scope (cancel_character_image for scene pictures), and points to get_character_queue for verification. An agent has everything it needs to choose between the two cancel tools.

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