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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the HTTP endpoint and what a meter record carries (units, reading frequency, owning asset/location), but says nothing about pagination behavior, result caps, or auth scope beyond what the limit/offset schema already implies.

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 sentences, front-loaded with the purpose, the parenthetical clarifying what a meter is, and the endpoint. No filler or redundancy.

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 11 optional parameters and no output schema, the description should carry more of the return-shape and pagination story. It describes the record contents reasonably but omits paging/next_offset behavior and total counts, leaving gaps for an agent assembling a listing call.

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% across all 11 parameters, so the schema fully documents filtering, includes expansion, ordering and date bounds. The description only alludes to the returned attributes and adds no syntax or format detail beyond the schema, so the 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?

States a specific verb (List) and resource (meters), and even disambiguates the domain concept with examples (hours, mileage, temperature) plus the fields returned. It implicitly separates itself from upkeep_get_meter and upkeep_list_meter_readings, but never names those siblings explicitly.

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?

Usage is only implied by the noun 'List' and the GET /meters endpoint reference. There is no statement about when to prefer this over upkeep_get_meter for a single meter or upkeep_list_meter_readings for readings, and no exclusions or prerequisites are given.

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