psu_set_mode

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

No annotations are present, so the description carries full behavioral burden. It only states that the mode is set, without mentioning side effects, required conditions (e.g., output disabled), or how tracking affects channel behavior. This is a minimal disclosure for a mutating operation.

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 compact and front-loaded with the purpose, followed by a concise Arg line. Every word is informative, and it avoids repeating schema details while adding the missing enum values.

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 setter, the description provides the necessary allowed values and a clear purpose. However, it omits explanation of what tracking mode actually does and any situational context, leaving the agent without enough information to decide which mode is appropriate.

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 exposes only a string field with no enum or description. The description compensates by listing the three valid values (INDEPENDENT, SERIES, PARALLEL), which is essential for correct invocation. It does not explain the meaning of each mode, but it covers the required input space.

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 ('Set') and a clear resource ('channel tracking mode on the power supply'), making the tool's function unambiguous. It distinguishes itself from sibling tools like psu_set_voltage and psu_set_current without confusion.

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?

No guidance is provided about when to use tracking mode, what alternatives exist, or any prerequisites or consequences. The agent must infer usage purely from the tool name and the mode list, which is not explicit guidance.

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