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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the default result ordering and the shape of returned records, but says nothing about pagination behavior, rate limits, or what happens for a meter with no readings.

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?

Two compact sentences: what you get, what identifies it, and the ordering all come first, and the raw endpoint is relegated to the tail. No sentence is wasted.

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?

With no output schema, the parenthetical describing returned fields (value, date, who recorded it) fills the main gap, and the schema covers paging and filtering. Only a note on empty results or cross-referencing upkeep_get_meter 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%, with limit, offset, order_by and the read_after/read_before date bounds all documented inline, so the baseline is 3. The description adds no extra meaning to those parameters — 'newest first' merely restates the order_by default already in the schema.

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?

Names a specific verb and resource (readings for one meter) and scopes it to a single meter, plus previews the returned fields and sort order. It doesn't explicitly contrast with the write sibling upkeep_add_meter_reading or with upkeep_get_meter, leaving some differentiation implicit.

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 implies the context of use by requiring a meter id and stating results are newest first, but it never says when to pick this over upkeep_get_meter or upkeep_add_meter_reading, nor any prerequisites for the meter existing.

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