m8811_set_voltage

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

Annotations only state non-read-only/non-destructive hints; the description adds that the output must be off and that the setting is verified by read-back. This adds meaningful behavioral context beyond the structured annotations.

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?

A single sentence that front-loads the action and range, then adds the key precondition and verification behavior. Every clause is informative and there is no redundant content.

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 one-parameter setter with an output schema present, the description covers the action, range, precondition, and verification. No critical information is missing for correct invocation.

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 schema only defines 'voltage_v' as a number, with no description. The tool description compensates by specifying the valid range 0-30 V and implies the unit is volts, giving the single parameter concrete meaning beyond the schema.

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?

Description states a specific action ('Set 0-30 V') on a specific resource (m8811 voltage) and includes the valid range. It is clearly distinguished from sibling tools such as m8811_set_current and m8811_set_voltage_protection by naming the resource and range.

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?

It provides a concrete precondition ('while output is off'), giving clear context for when the tool can be used. It does not explicitly name alternative tools or exclusions, but the resource-specific wording makes the intended use unambiguous.

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