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

Annotations already establish readOnlyHint=false and destructiveHint=true, and the description adds useful precision: the write effect is limited to blocking new submissions and does not prevent existing reports from being reviewed. This goes beyond the structured annotations and does not contradict them.

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 short sentence with a semicolon cleanly separates the action from its non-destructive consequence. There is no filler or repetition; every word 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?

With no output schema, low schema coverage, and many funded-task siblings, the description leaves open whether the caller needs an admin role, how to undo the pause, and what request_id represents. It is adequate as a label but not as complete invocation guidance.

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 33% (just agent_key), and the description adds no meaning for task_id or request_id. The request_id role (likely for idempotency given idempotentHint=true) is left unexplained, so an agent cannot confidently construct valid input.

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 concrete action ('Pause new submissions') and a key consequence ('existing reports remain reviewable'), so it is not a tautology. It differentiates from cancel/resume by scope, but it never explicitly distinguishes this tool from the similarly named sibling speedbot_exchange_funded_task_admin_pause.

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?

There is no guidance on when to prefer this tool over alternatives such as admin_pause, resume, cancel, or kill_switch, and no prerequisite such as role or task ownership. The only usage signal is implied by the word 'Pause,' which is too thin for the crowded funded-task workflow.

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