get_inverter_info

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine value beyond that: it establishes the data is static rather than live status, and it discloses the fan-out behavior when inverter_id is omitted (reads every configured inverter). It does not mention connection prerequisites or error behavior, but the core behavioral profile is clear.

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?

Front-loaded with the resource and payload fields, followed by a compact Args block. Every sentence carries information; the docstring-style 'Args:' formatting is slightly mechanical but not wasteful.

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?

An output schema exists, so return values need no explanation, and the single parameter is documented. The main omission is any routing help relative to the many sibling status/read tools, but for a simple static-read tool the description is otherwise 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 0%, so the description must carry the parameter alone, and it does: inverter_id is identified as a Modbus device id, marked optional via 'Omit', and its fallback semantics are spelled out. This fully compensates for the missing schema description, though it adds no range/format detail.

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?

States a specific verb+resource ('Static inverter information') and enumerates the returned fields: model, serial number, firmware and ratings. The word 'Static' implicitly contrasts with the dynamic sibling get_inverter_status, but it never names that sibling, so the distinction is left to inference.

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 only usage guidance is parameter-level: 'Omit to read every configured inverter.' There is no explicit when-to-use-this vs get_inverter_status or the other status tools, so tool selection is only implied by the 'static' framing.

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