get_pv_power

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly explains the two behaviors: instance=0 returns all discovered devices with readings plus total_power, while instance=N returns a single device dict. This goes beyond the schema and gives actionable behavioral context.

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 with no redundant wording. The main purpose is front-loaded, and the parameter detail follows in a compact, readable format.

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?

For a simple single-parameter getter, the description covers the core behavior and output shape. An output schema exists, so detailed return structure can be obtained there. Minor gaps like units or error handling do not undermine usability.

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 schema only defines instance as an integer with default 0 and no description. The tool description compensates by explaining the meaning of instance=0 and instance=N, fully covering the semantic range of the parameter.

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 and resource ('Get PV/solar charger power data'), clearly identifying the tool's function. It is distinct from siblings like get_battery_soc, get_grid_status, and get_inverter_status, which target different data domains.

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?

Usage context is implied by the resource name but not explicitly articulated. The description explains what instance values do but does not state when to prefer this tool over alternatives or mention any exclusions. Minimal but adequate.

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