Battery Status

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds behavioral context by listing the specific data returned (alarms, history) and the need for a unitId. No contradiction with 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?

Two sentences, front-loaded with the core action. Every part is informative: the data returned and a practical tip for finding unitId. No wasted words.

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, description does not need to explain return format. It sufficiently lists key data categories, explains how to identify the battery monitor, and complements the parameter descriptions. Complete for an agent to select and invoke correctly.

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 high (100%), so baseline is 3. Description adds value by advising to use victron_discover to find the unitId, and by contextualizing what parameters are for (e.g., unitId for battery monitor).

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?

Description uses specific verb 'Get' and resource 'detailed battery monitor data', listing concrete data points (SOC, voltage, current, etc.). Distinguishes from sibling tools by clearly scoping to battery monitor status and referencing 'victron_discover' to find unitId.

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?

Provides clear usage context: specify unitId, check victron_discover. Implicitly when battery data needed. Does not explicitly exclude alternatives like victron_solar_status, but the tool name and content make its domain clear.

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