psu_measure_power

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

With no annotations, the description carries the full behavioral burden. It states the operation ('measure actual output power') and the word 'actual' usefully implies a live reading rather than a setpoint, but it does not disclose whether the channel must be enabled, whether this is non-destructive, or any timing/error behavior.

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 two short lines with the purpose front-loaded and an Args section for the parameter. Every sentence earns its place.

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 single-parameter measurement tool with an output schema available, the description covers the essential purpose and parameter range. It could be more complete with explicit usage guidance or preconditions, but nothing critical is missing for this low-complexity tool.

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 the schema only says 'Channel' as an integer. The description compensates fully by defining the single parameter as 'Channel number (1, 2, or 3)', adding the valid values the schema omits.

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 uses a specific verb ('Measure') and a specific resource ('actual output power on a power supply channel'), which clearly distinguishes it from siblings like psu_measure_voltage and psu_measure_current.

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?

There is no guidance on when to choose this tool over psu_measure_voltage/psu_measure_current or psu_get_*, and no mention of prerequisites such as the output being enabled. Usage context is only implicit in the verb and resource.

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