get_snapshots

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

With no annotations, the description carries the full burden of disclosure. It reveals useful behavioral details: the snapshots are raw, cover the last ~60 minutes, are sampled every ~10 minutes, and include cell voltages, delta, SOC, and balancing state. It does not explicitly state that it is read-only, but the 'raw snapshot' phrasing implies observation.

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 two sentences, front-loaded, and every clause contributes meaning: time window, cadence, and content. No filler or irrelevant details.

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 read-only tool with no parameters and no output schema, the description sufficiently explains what is returned, the time range, and the sampling interval. It supports confident tool selection without requiring additional detail.

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 input schema has zero parameters, so coverage is vacuously 100%. The baseline for zero-parameter tools is 4, and the description does not need to add parameter semantics because none exist.

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 that the tool returns raw battery pack snapshots for the last ~60 minutes, with a specific cadence of one per ~10 minutes, and lists the included metrics. This distinguishes it from siblings like get_cell_voltages or get_balance_trend, though it does not explicitly contrast with them.

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 provides no guidance on when to use this tool versus the many sibling get_* tools. There are no explicit alternative recommendations or conditions for use, so the agent must infer from the raw snapshot context alone.

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