pause

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

With no annotations, the description carries the full behavioral burden. It adds real value by disclosing that the pause halts prepares and submissions and is 'receipted' (a side effect not otherwise documented), but it omits reversibility, permissions/authorization needs, and whether the pause is global versus scoped.

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?

Three terse clauses, front-loaded with the highest-signal term ('KILL SWITCH'), and every sentence adds information (scope, effects, receipt). No wasted words.

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 high-impact, irreversible-sounding mutation with no annotations and no output schema, the description conveys key semantics (immediacy, global scope, receipt side effect) but leaves significant gaps: how to undo, whether authorization is required, and what the undocumented reason parameter is for.

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 coverage is 0% and there is one optional parameter (reason) that the description never mentions. Since a parameter exists, the 0-param baseline of 4 does not apply, and the description does nothing to explain the purpose or expected content of 'reason'.

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?

Names a specific action (pause) and states its scope ('everything') and effects ('prepares and submissions stop'), which distinguishes it from resumption/tracking siblings like resume and get_tracker. It stops short of explicitly naming resume as the inverse, but an agent can identify the operation without opening the schema.

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 'KILL SWITCH' framing implies an emergency/urgent context, so when-to-use is inferable. However, there is no explicit statement of when to use this versus resume, no prerequisites (e.g., authorization), and no guidance on when it is inappropriate.

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