get_consumption

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

With no annotations, the description carries the full burden. It usefully discloses the unit (kWh) and the output granularity per resolution, but says nothing about authentication requirements, defaulting behavior, coverage limits, or error conditions for an unannotated data-fetch tool.

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 well-formed sentence with the resource and the key variable (resolution) front-loaded. No padding, though for a 6-parameter tool it borders on under-specification rather than pure conciseness.

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?

For a 6-parameter read tool with no annotations and no output schema, the one-line description is the minimum viable: it conveys the resource and granularity but omits output shape, defaults, and any relationship to sibling tools like list_meters or get_last_meter_reading.

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% and the resolution enum is fully documented in the schema, so the description's restatement of 'day = 15-minute steps, week/month = daily totals' adds no meaning beyond it. All other parameters (bpNumber, meterCode, contractId, meterSerial) are left entirely to 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?

States a specific resource (smart-meter consumption in kWh) and enumerates the three temporal granularities, which is more than a restatement of the name. It implies a historical time-series read, distinguishing it from get_last_meter_reading, though it never names that sibling.

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 explicit when-to-use guidance, no mention of prerequisites (auth, contract/meter selection) and no routing to alternatives such as get_last_meter_reading or list_meters. The agent must infer all of this from the schema.

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