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

Annotations already declare destructiveHint=true, and the description adds real behavioral nuance beyond them: claimed plans retain recovery references and submitted tasks are not cancelled. This clarifies the blast radius of the operation, though it does not address auth requirements or confirm_token semantics.

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 terse sentences, with the core action front-loaded and the caveat about retained references following. No filler, though the second sentence is somewhat dense and could be clearer.

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 deny action with no output schema, the behavioral caveats are useful, but the complete absence of parameter documentation (especially the required confirm_token) leaves a notable gap an agent must fill from inference alone.

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% and the description says nothing about either parameter. The required confirm_token and the mctx connection_context pattern are documented nowhere, so an agent gets no guidance on what values to supply.

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?

The description states a specific verb and resource: 'Deny an unclaimed TikTok structural clone.' Combined with the title ('Discard a TikTok structure clone draft') it is clear this terminates a pending clone. It does not explicitly name the sibling confirm tool, but the prepare/confirm/deny pattern makes the purpose inferable.

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 qualifier 'unclaimed' implies the condition under which denial applies, and the sibling set (copy_ad_clone_structure_confirm) makes the alternative obvious. However, the description never explicitly states when to choose deny over confirm or what prerequisites exist, leaving usage to inference.

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