emergency_trip_input

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

Discloses auth token requirements and side effect of triggering software e-stop. No annotation provided, but description covers key behavioral aspects. Lacks specifics on idempotency or error responses.

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?

Front-loaded with purpose, then context, differentiation, auth, parameter details, and see-also. No superfluous text; every sentence adds value.

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?

Covers all four parameters and authentication. Missing return value or error handling details, but for a simple e-stop trigger, this is largely sufficient given no output schema.

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?

With 0% schema description coverage, the description compensates fully by explaining each parameter's purpose, default values, and conditional requirements (e.g., token).

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?

Clearly states its purpose as 'Trip emergency stop from an external hardware bridge' and explicitly differentiates from emergency_stop() which is for agent/software-initiated stops.

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 when to use (physical input devices) and when not (use emergency_stop for software stops). Provides alternative tool names and details authentication requirements.

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