DC-DC Converter Status

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and idempotency. The description adds listing of specific data fields but no additional behavioral details like error handling, rate limits, or authentication needs. This meets the baseline with annotations present.

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 only two sentences, front-loading the purpose and data fields in the first sentence and a concise prerequisite hint in the second. No unnecessary words—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 complexity (8 parameters, output schema exists), the description covers the essential purpose and return data. It does not mention the two transport options (modbus/mqtt) or how to choose them, but schema descriptions handle that. Output schema makes return format specification unnecessary. Minor gaps in transport guidance prevent a 5.

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?

All 8 parameters have descriptions in the schema (100% coverage), so the schema already defines them. The description only provides one extra hint about using victron_discover for the unit ID. This is adequate but does not significantly enhance parameter understanding beyond the schema.

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 'Get' and explicitly names the resource 'Orion XS DC-DC converter', listing detailed data fields (battery voltage, current, temperature, etc.). This clearly distinguishes it from sibling tools like victron_battery_status or victron_inverter_status, which target different components.

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 recommends using victron_discover to find the unit ID, providing a clear prerequisite. However, it does not explicitly state when to use this tool versus alternative status tools; context of sibling names implies it is for DC-DC converter status, but explicit guidance would improve the score.

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