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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: only unclaimed plans are discarded, claimed plans retain recovery references, and already-submitted tasks are unaffected — all non-obvious consequences of the call.

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 stated first and the caveats after. Every clause carries information that the schema and annotations do not.

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 mutation with no output schema, the description explains the outcome well but omits the required token's origin and any error/eligibility conditions. It is adequate but leaves an agent guessing on the one required parameter.

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 in particular has no explanation of its provenance (presumably a prepare/recreate step) or lifetime, so an agent gets no help from the text on how to supply it.

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 ('Deny an unclaimed TikTok recreation') with a scope qualifier that the title alone does not carry. An agent can pair it with the sibling campaigns_recreate_confirm by the deny/confirm naming, though the description never names that alternative explicitly.

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 'unclaimed' implies a precondition and 'this does not cancel submitted tasks' draws a boundary, but the description never states when to choose this over campaigns_recreate_confirm or what makes a recreation 'unclaimed'. Usage is inferable rather than spelled out.

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