trigger_kill_switch

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

No annotations are provided, so the description carries the full burden. It usefully discloses that a tool call cannot clear the kill switch, signaling irreversibility. However, it omits other critical behavior: what state changes occur, whether authentication or confirmation is required, and what the system does after latching.

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?

Two very short sentences with the most important fact (irreversibility) front-loaded. There is no filler, and every sentence adds essential information about the tool's behavior.

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-stakes, irreversible action with no annotations and no output schema, the description is too sparse. It does not explain what the kill switch stops, what side effects occur, or what safety checks may be needed, leaving significant gaps for an agent to safely invoke it.

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?

This tool has zero parameters, so parameter semantics are not a factor. The baseline of 4 applies because there is no schema parameter information that the description needs to supplement.

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 ('Latch') and resource ('the kill switch'), making the core action clear. However, it does not explain what the kill switch actually affects (e.g., halts trading, cancels orders, locks the system) or provide any sibling differentiation, leaving the full purpose partly opaque.

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 implies this is for an emergency latch, but it gives no explicit when-to-use guidance, no prerequisites, and no alternatives. An agent knows the action is irreversible but lacks context about when this should be invoked versus other tools.

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