PV Inverter Status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating a safe read operation. The description adds the list of returned data fields, which provides some behavioral insight, but does not disclose potential side effects (none expected) or other traits beyond 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?

The description is very concise: two sentences. The first states the tool's purpose and data fields, the second gives a crucial prerequisite. No superfluous information.

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 output schema exists (mentioned in context) and the description lists the returned data fields, the description is complete for this read-only tool. The parameters are fully described in the schema, and the prerequisite is addressed.

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%, with each parameter described. The description reminds to use vctron_discover for the unitId, adding context beyond the schema, but does not significantly enhance understanding of each parameter's purpose beyond the schema descriptions.

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 it retrieves AC-coupled PV inverter data and lists specific data fields (power per phase, voltage, etc.), distinguishing it from siblings like victron_solar_status, which might cover other solar aspects. The verb 'Get' and resource 'AC-coupled PV inverter data' are explicit.

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 a clear prerequisite: 'Use victron_discover to find the PV inverter unit ID.' It implicitly advises to use vctron_discover before this tool, but does not explicitly state when to use this tool versus alternatives like victron_solar_status or victron_inverter_status.

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