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

Annotations already flag this as destructive, non-read-only and open-world, so the safety bar is pre-set. The description adds genuinely useful behavior beyond that: the ref is single-use ('consume one'), the dispatch happens exactly once, uncertain results are never replayed, and recovery happens through operations_get on the authorization route.

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 dense sentences, front-loaded with the core action and followed by the failure-handling rule. Every clause carries weight, though 'on the original authorization route' is slightly cryptic phrasing.

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 idempotency and recovery well but omits the prerequisite flow (budget_prepare), the meaning of connection_context, and any notion of what is returned on success.

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%, so the description must carry parameter meaning. It references approval_ref only obliquely ('one budget approval_ref') without format or source guidance, and never mentions connection_context at all, leaving one of the two parameters fully undocumented.

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 gives a specific verb and resource: consuming an approval_ref and dispatching the recorded TikTok budget change. It clearly implies the confirm step of a prepare/confirm pair, but never names budget_prepare as the thing that produces the ref, so sibling differentiation is inferred rather than stated.

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 implies the tool is used to confirm a previously recorded change and gives a strong recovery path for transport-uncertain results (operations_get). However it never explicitly states the precondition (a change prepared via budget_prepare) or when to use this rather than budget_prepare/approval alternatives.

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