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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description doesn't need to restate the safety profile. It adds genuinely useful behavioral context the annotations cannot convey: idempotency semantics ("One durable task; a lost response may be recovered with the same unexpired token") and an explicit anti-replay warning, which directly addresses the risk of duplicate execution.

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?

Three sentences with the purpose front-loaded and no filler. Each sentence carries distinct information: action, recovery behavior, and replay prohibition.

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 covers the approval prerequisite and idempotency but omits what a successful confirmation returns, the meaning of connection_context, and how the token is obtained. Annotations carry the safety profile, so the gap is moderate rather than severe.

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 both parameters, so the description must carry the burden. It references an "unexpired token" that maps loosely to confirm_token, but gives no format, lifetime, or sourcing detail, and the connection_context parameter is entirely undocumented in both schema and description.

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 names a specific verb and resource ("Confirm one prepared TikTok task recreation") and scopes it to the confirm step, which distinguishes it from the sibling deny and prepare tools. It stops short of naming campaigns_recreate_from_task or campaigns_recreate_deny as its counterparts, so differentiation relies on the reader's inference.

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?

It gives a precondition ("after explicit approval") and a caution ("Never replay a prior task directly"), which implies the when-to-use context. However, it never names the sibling alternative that prepares the task or the deny counterpart, leaving the routing decision implicit.

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