get_all_batteries

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

With no annotations, the description must carry behavioral disclosure on its own. It communicates that the data is 'live' and lists the provided fields, which implies a read-only status query. However, it does not explicitly state whether the operation is side-effect-free or if any caching or rate limits apply.

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 a single, well-structured sentence that front-loads the core purpose and lists the key data fields. Every word contributes useful information with no redundancy or fluff.

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 there is no output schema, the description provides a helpful field list (SOC, power, voltage, temperature, charging state) that conveys the return content. It is slightly incomplete because it does not explicitly state that the result is an array of battery statuses, but the phrase 'all batteries' strongly implies that structure.

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 there is nothing to clarify. The description's mention of the returned metrics fully covers the only meaningful semantic content, matching the baseline of 4 for parameterless tools.

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 returns the live status of all Felicity batteries, listing specific metrics (SOC, power, voltage, temperature, charging state). This distinguishes it from siblings like get_battery (single battery) and get_health (health-focused) by scope and content.

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 gives no explicit guidance on when to use this tool versus alternatives. While 'all batteries' implies a fleet-wide view, it does not mention specific use cases or contrast with sibling tools such as get_battery or get_fleet_summary.

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