clear_emergency_stop

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

No annotations are present, so the description carries the full burden. It only states 'Clear emergency stop' without disclosing behavioral traits such as whether it resets all safety conditions, requires authentication, or has side effects. This is minimal disclosure for a safety-related operation.

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—a three-word phrase. It is front-loaded and without waste. However, it is arguably too terse, lacking any additional context that might be helpful, though this is balanced by its simplicity.

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?

Although the tool has an output schema, the description does not explain what happens after clearing, what the output represents, or how this relates to emergency_stop. Given the presence of sibling tools and the safety-critical nature, the description is incomplete in contextual 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?

The input schema has zero parameters, so baseline 4 applies. The description does not need to elaborate on parameters, and the empty schema is fully consistent with the action being a parameterless command.

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 'Clear emergency stop' uses a specific verb ('clear') and a specific resource ('emergency stop'), clearly identifying the action. It distinguishes itself from siblings like 'emergency_stop' and 'stop' by indicating a reset/clearing operation rather than activation.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, conditions, or the relationship to 'emergency_stop'. The usage is only implied by the name, but the description itself does not state when to invoke it.

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