set_current

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

With no annotations, the description must fully disclose behavior. It states the effect (set current limit) and rejection condition, but omits important details: whether changes take effect immediately, if they persist, return values, or side effects like output state changes. More context is needed for a write 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?

Two concise sentences, front-loaded with the main purpose. No unnecessary words or repetition. Every sentence adds value.

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 the tool (one param, no output schema, no annotations), the description covers the core functionality but lacks completeness on success indicators, error behavior, and immediate effects. It is adequate but not thorough.

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 single parameter 'amps' has 0% schema coverage. The description adds unit (amps) and range (0-5 A), which is helpful but incomplete—it doesn't specify data type (float vs integer), precision, or step size. For a single param, more detail would improve clarity.

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 the verb 'Set' and the resource 'output current limit', with a specific range (0-5 A). It distinguishes from sibling tools like set_voltage and set_ocp by specifying it's for constant-current operation.

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 description mentions that the value is rejected if outside the model's range, providing a basic condition for when-not-to-use. However, it lacks explicit guidance on when to use this tool versus alternatives like set_voltage or set_output, and does not specify prerequisites such as output state.

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