charger.stop_slot

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

With no annotations, the description carries full burden. It discloses the key behavior of bypassing profile validation, but does not cover other traits like potential destructive effects, reversibility, or error handling.

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 at 6 words, front-loading the critical 'emergency stop' action. Every word earns its place, focusing on the unique aspect of bypassing validation.

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 simple tool with one parameter and no output schema, the description is fairly complete. It conveys the purpose and the exceptional behavior (bypassing validation), though it lacks details about failure modes or slot numbering conventions.

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 description coverage is 0% for the 'slot' parameter. The tool description does not explain what the slot parameter represents beyond the integer range already in the schema. No additional semantic value is provided.

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 clearly states an 'emergency stop for one slot' and distinguishes itself by noting it 'bypasses profile validation.' This sets it apart from sibling tools like charger.stop_all, which stops all slots, and charger.start.

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 phrase 'emergency stop' implies urgent scenarios, but there is no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or contrast with other stop operations.

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