list_solarbanks

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

Describes heuristic identification and fallback to returning all devices, but does not explicitly state it is read-only or non-destructive. Since annotations are missing, the description could be slightly improved by noting it has no side effects.

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?

Four sentences with no wasted words; first sentence immediately states the core purpose. Information is front-loaded and efficient.

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?

Complete for the tool's simplicity: no parameters, has output schema, and the description covers behavior, fallback, and guidance for further action. No gaps.

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?

No parameters exist, so the description correctly adds no parameter details. Baseline score applies as schema coverage is 100% vacuously.

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 it lists devices identified as Solarbanks or expansion battery packs using heuristic matching on model/type/name fields, distinguishing it from the sibling tool list_devices which lists all devices without filtering.

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?

Explicitly explains when to use (to find Solarbanks) and what to do if no match (use get_device on any serial number for unfiltered detail), providing clear alternatives and fallback behavior.

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