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

Annotations already provide readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is largely structured. The description adds that the effect is on submissions for a single task and that the action is a reversible pause/resume toggle, but it does not explain unintended consequences or authorization requirements beyond the 'Admin:' label.

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 that front-loads the admin scope and the core action. It is appropriately concise, though the brevity comes at the cost of missing important behavioral and parameter context.

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 an admin mutation tool with five parameters, no output schema, and sparse schema descriptions, this description is too thin. It does not explain how paused maps to behavior, what happens to in-flight submissions, or what admin authentication is expected, leaving the agent to infer critical invocation details.

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 20%, with paused, task_id, and request_id left undocumented. The description's phrase 'pause or resume' only loosely maps to the paused boolean and says nothing about the request_id or admin_token/agent_key authentication parameters.

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 clear verb-resource pair ('pause or resume submissions') and scopes it to 'one task', with the 'Admin:' prefix signaling elevated privileges. It is distinct enough from the non-admin pause/resume siblings, though it does not explicitly name or contrast them.

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 gives no guidance on when to prefer this tool over sibling admin tools such as speedbot_exchange_funded_task_admin_hide, admin_kill_switch, or the non-admin pause/resume variants. 'Admin:' implies an audience but does not state prerequisites, exclusions, or alternatives.

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