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

Annotations already declare destructiveHint true and readOnlyHint false; the description adds the concrete scope of the effect (all automatic payouts and refunds). It does not state whether the action is reversible, what happens to in-flight payments, or how 'paused' interacts with the paused boolean.

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?

One front-loaded sentence with no filler, and 'Admin' clearly marks the audience. The brevity borders on under-specification for a destructive admin control, but the sentence itself is appropriately sized.

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 admin tool with no output schema, this is incomplete: it omits reversibility, auth requirements (despite admin_token/agent_key), return behavior, and clarification of what 'all automatic' includes. Annotations cover the safety profile but not the operational details needed to call it correctly.

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 only 25%, so the description needed to explain paused, request_id, and admin_token. It only indirectly maps 'pause' to paused and leaves true/false semantics, the required request_id, and auth token roles 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?

States a specific action (pause) on a specific resource (all automatic funded-task payouts/refunds) and identifies the admin audience. However, it does not differentiate from the closely named sibling speedbot_exchange_funded_task_admin_pause, leaving ambiguity about which admin pause tool to choose.

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?

Provides only an audience prefix ('Admin:') and a general action. It gives no when-to-use guidance, no exclusions, and no reference to the similarly named sibling admin_pause tool, so an agent has no basis for routing between them.

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