output_off

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

No annotations, so description carries full burden. It discloses immediate power cut, the warning about mid-flash, and the 'never gated' behavior indicating no delays or conditions, fully transparent for a simple on/off tool.

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 concise sentences with no fluff. Every word adds value: 'Switch the output OFF' (purpose), 'cutting DUT power immediately' (behavior), 'Do not use mid-flash' (usage), '(Never gated...)'(transparency).

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 simplicity of a turn-off function and absence of output schema, the description covers primary purpose and usage constraints. However, the missing explanation of the 'port' parameter is a notable gap, preventing full completeness.

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 coverage is 0% and description does not explain the 'port' parameter (optional, default null). The user is left wondering what port refers to, which is essential for proper usage.

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 it switches the output OFF and cuts DUT power immediately, using specific verb and resource. It implicitly distinguishes from sibling 'output_on' by stating 'OFF'.

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?

Provides explicit when-not-to-use: 'Do not use mid-flash.' Adds 'Never gated - cutting power is always allowed' indicating no prerequisites. However, does not explicitly name alternatives like 'output_on' for power on, but context makes it clear.

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