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

With no annotations, the description carries full behavioral burden. It discloses the one-shot consumption semantics ('never replayed'), the action taken ('dispatch'), and the recovery approach when the result is uncertain. This goes beyond a generic confirmation description, though it does not cover permissions or side effects in detail.

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 tightly written sentences with no filler. The core action and idempotency constraint are front-loaded, and the recovery instruction earns its place.

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 single-parameter confirmation tool with no output schema and no annotations, the description covers purpose, one-shot behavior, mutation, and failure recovery. It is slightly thin on expected return values and explicit prerequisite steps, but the reference to 'original authorization route' implies the flow.

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?

The schema provides only the pattern and format, with 0% description coverage, so the description must add meaning. It clarifies that approval_ref is a budget approval reference tied to an original authorization route, but it doesn't explain where the value comes from or how to obtain it beyond the pattern.

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: it consumes a budget approval_ref and dispatches the exact recorded TikTok change. This distinguishes it from preparation tools like budget_prepare, though the phrase 'dispatch the exact recorded TikTok change' is somewhat jargon-heavy.

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 description implies this is the confirmation step after an authorization route, and it gives a specific recovery path via operations_get for transport-uncertain results. However, it does not explicitly state when to prefer this over siblings like bid_confirm, nor does it describe prerequisites such as having called budget_prepare.

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