charger.get_voltage_curve

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

With no annotations, the description must convey behavioral traits. It only states 'Read' (non-destructive) and 'No polling' (no repeated requests). It does not disclose response format, speed, error conditions, or slot availability requirements, leaving significant gaps.

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?

A single 12-word sentence is concise and front-loaded. However, its brevity sacrifices necessary detail on parameters and output, making it less effective than a slightly longer, more informative description.

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?

The tool has 2 parameters, no output schema, and no annotations. The description does not explain what a 'voltage time-series' is, what the output resembles, or how parameters affect behavior. This leaves the agent with insufficient context to use the tool correctly.

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 description makes no mention of parameters. The input schema has 0% description coverage, so the agent must rely solely on schema constraints (e.g., slot range) without understanding parameter meaning (e.g., timeout unit or effect). Description adds zero value for parameter interpretation.

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 states a clear action ('Read') and resource ('charger-stored app-style voltage time-series for one slot'), effectively distinguishing from sibling tools like 'charger.export_voltage_curve' (export vs read) and 'charger.read_slots' (slot status vs curve).

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 phrase 'No polling' implies a one-shot read, but the description does not provide explicit guidance on when to use this tool versus alternatives (e.g., when to poll vs get a single point). No exclusions or prerequisites are mentioned.

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