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

Annotations already cover readOnly, idempotent, and openWorld hints, so the safety profile is known. The description adds valuable behavioral context beyond that: it states the response contains user comments and fault reports with specific outcome values, alongside registry status and last-verified date, and explains pagination semantics ('a page reports truncated', 'repeat with nextOffset') and ordering ('newest-first'). No contradiction with annotations.

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 three sentences, with the core purpose front-loaded in the first sentence. The second sentence summarizes the output content without unnecessary elaboration, and the third covers pagination concisely. There is no fluff or repetition; every clause earns its place.

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 the tool's moderate complexity (3 params, one required), existing output schema, and annotations covering safety, the description provides everything needed to call it correctly: purpose, output content, pagination handling, and ordering. The output schema will document return values, so nothing critical is missing.

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% for all three parameters, so the schema already fully documents `id`, `offset`, and `maxresults` including defaults and maximums. The description does not add new parameter-level details beyond what the schema provides; it reinforces the offset pagination behavior but does not extend beyond it. Per the rubric, a baseline of 3 is appropriate.

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 a specific verb ('Read') and a clear resource ('community check-ins and comments for one Open Charge Map station'), and immediately differentiates itself from siblings by framing it as 'the real-world reliability signal beyond the operator-reported registry status.' An agent can unmistakably identify this as the tool for retrieving user comments for a specific station, distinct from find_stations (search), get_station (registry details), and lookup_reference (reference data).

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 clear context on when to use the tool ('beyond the operator-reported registry status') and gives concrete usage for pagination ('when a page reports truncated, repeat the call with the reported nextOffset'). It does not explicitly name alternative tools or specify when not to use it, but the purpose framing effectively guides selection. The pagination guidance is a strong practical instruction.

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