AC Load / Current Sensor

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, indicating safe read operations. The description adds context about the returned data (per-phase power, voltage, etc.) but does not disclose further behavioral traits like side effects or auth requirements beyond what annotations provide.

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 extremely concise, consisting of two sentences with no filler. It front-loads the main purpose and immediately provides context and prerequisite.

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 tool has 8 parameters (1 required), 100% schema coverage, and an output schema, the description adequately covers the core functionality and the discovery prerequisite. It does not explain how to get the host or defaults, but those are covered in the schema. For a read-only status tool, this is sufficient.

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 100%, so all 8 parameters have descriptions in the input schema. The description adds minimal extra value for parameters, only mentioning 'Use victron_discover to find the unit ID' for the unitId parameter. No additional syntax or format details are provided.

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 'Get' and the resource 'AC load and current sensor data' with specifics like per-phase power, voltage, etc. It distinguishes from siblings by specifying 'Used for AC current sensors measuring PV inverter output or other AC loads.'

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 provides context on when to use the tool ('Used for AC current sensors measuring PV inverter output or other AC loads') and references a sibling tool ('Use victron_discover to find the unit ID'). However, it does not explicitly state when not to use it or compare with alternatives like other sensor status tools.

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