solar_devices

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

The description fully explains the return format (dict with device classes, list of devices with bus index and serial number) and the meaning of empty lists. Since no annotations are provided, the description carries the full transparency burden and does so completely.

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 three sentences front-loaded with the primary action, followed by detailed output format and a use case. Every sentence adds value without redundancy.

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 tool has no parameters and no output schema, the description is complete: it explains the purpose, output structure, and interpretation of results. It adequately covers the tool's functionality.

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?

There are no parameters (empty input schema), so the baseline is 4. The description does not need to add parameter info, and it correctly focuses on the output behavior.

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 clearly states the tool lists all devices connected to the Fronius inverter system, using specific verb 'lists' and resource 'devices'. It distinguishes from sibling tools like 'configure_inverter' or 'solar_battery' by covering all device classes.

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 includes a use case ('useful for verifying system topology or diagnosing missing devices'), which implies when to use. It lacks explicit exclusions or direct comparisons to sibling tools.

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