get_battery

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

No annotations are present, so the description carries the full burden. While 'Returns' implies a read-only operation, there is no disclosure of side effects, prerequisites, or limitations. This matches the 'update_drive' example that scored 2 for lacking behavioral context.

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, 12-word sentence that is front-loaded with the key verb and resource. Every word adds value with no redundant filler or restatement of the tool name.

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 simple getter with one optional parameter, the description is minimally viable. It lists the returned fields but omits units, error conditions, or vehicle wake state. The lack of annotations and output schema increases the burden, yet the simplicity of the tool keeps it at a 3.

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 description coverage is 100%, with the vin parameter fully documented including default behavior via TESSIE_DEFAULT_VIN. The description adds no parameter detail, but the schema covers it, so baseline 3 applies.

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 uses the specific verb 'Returns' and identifies the resource (battery) plus a detailed list of data fields (level, range, voltage, temperature, energy stats). This clearly differentiates it from siblings like get_battery_health or get_vehicle_state.

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?

No guidance is provided on when to use this tool versus alternatives. The description is purely functional and does not mention preferred use cases, exclusions, or sibling tools.

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