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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the useful context that results are individual sub-meter readings tied to billing cycles and sourced from Report 104, but says nothing about pagination, volume, or formatting behavior.

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 single sentence is front-loaded and free of padding, which is good. But for a 7-parameter tool it is under-specified rather than genuinely concise, so the brevity reflects missing information rather than efficient editing.

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?

An output schema exists, so return values need not be described. However, an agent still lacks usage context, sibling differentiation, and any documentation for seven undocumented parameters, leaving the definition incomplete for correct invocation.

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 0% across 7 parameters (unit, tenant, start_date, end_date, portfolio, property_ids, exception_only), and the description supplies no parameter meaning at all. An agent cannot tell what 'exception_only' toggles, what format the dates take, or whether property_ids is a list.

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 names a specific resource (individual sub-meter readings) and scoping (per billing cycle) plus the data source (Report 104), so the purpose is discernible. However, it does not distinguish this tool from close siblings like get_meter_rate_card, list_meter_types, or analyze_water_consumption, leaving an agent to infer the boundary.

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?

There is no when-to-use guidance, no prerequisites, and no naming of alternatives among the ~70 sibling tools. The 'Report 104' note implies a reporting origin but does not tell an agent when to prefer this over the rate card or water consumption tools.

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