List Sunsynk inverters

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is covered. The description adds value by specifying the exact fields returned and the fact that the sn is meant for cross-tool usage, which is behavioral context beyond the annotations. It does not mention pagination or ordering, but for a simple list tool this is acceptable given the annotation coverage.

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 concise sentences. The first sentence front-loads the purpose and enumerates the key fields; the second adds a practical usage tip. No filler or redundancy. The structure is efficient and easy to parse.

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 parameterless list tool with no output schema, the description adequately specifies what the agent can expect (the listed fields). Combined with the annotations (read-only, open-world), an agent has enough information to invoke the tool and interpret the result. Nothing critical is missing.

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 tool has zero parameters, so the schema already trivially covers 100% of them. Per the rubric, a baseline of 4 applies for 0 params. The description does not need to explain parameters and does not attempt to, which is appropriate.

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 action (list inverters) with a clear resource and enumerates the returned fields (sn, model, firmware, status, power, generation). This distinguishes it from sibling tools like sunsynk_list_plants, which targets a different resource, and from live_status/power_flow that provide real-time telemetry rather than a static list.

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 a clear use case: it is the tool to obtain the serial number (sn) for use with other tools. This implies a workflow dependency, though it does not explicitly mention alternatives or when not to use it. The context is sufficient for an agent to select it when needing an inventory of inverters.

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