Emergency Stop

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

The description fully discloses the destructive and side-effect behavior: cancelling all open orders, disabling order placement via control.json (persistent config change), and sending a Telegram alert (external notification). This goes beyond the destructiveHint annotation by specifying exact consequences.

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?

The description is extremely concise, using a single short sentence with a strong opening label ('PANIC BUTTON:') to emphasize urgency. It lists exactly three concrete actions with no filler or redundancy.

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?

Given the tool's simplicity and the presence of an output schema (not shown but assumed), the description covers all essential aspects: scope of cancellation, persistent configuration change, notification side effect, and usage constraint. No additional context is needed for an agent to invoke 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?

The only parameter 'reason' is optional with a default, but the description provides no explanation of its purpose or expected content. The schema also lacks a description, so the description adds no meaning to the parameter. Since it is a simple, self-explanatory name, a score of 2 is appropriate rather than 1.

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 specific verb ('cancel'), a clear scope ('ALL open orders'), and lists additional actions ('disable order placement', 'send a Telegram alert'). It distinguishes itself from sibling cancellation tools like cancel_order or cancel_order_set by emphasizing the global and emergency nature.

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?

Explicitly states 'Use only in emergency situations' and labels the tool as a 'PANIC BUTTON'. This gives clear guidance on when to invoke it versus normal cancellation tools, leaving no ambiguity about appropriate use.

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