get_consumption

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only mentions what data is returned and the parameters, omitting details like authentication requirements, error handling, data freshness, or whether the operation is read-only. The behavior beyond the basic functionality is not transparent.

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 concise, using three short lines to convey the main purpose and key parameters. It front-loads the overall goal and then lists parameters. However, the structure could be improved by using bullet points or clearer separation, but it remains efficient.

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?

While the output schema exists (which the description needn't explain), the description fails to cover all parameters (home_id missing) and lacks usage context relative to siblings. For a tool with three parameters, the description is incomplete, leaving gaps that the agent must infer or discover by trial.

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?

The schema has 0% description coverage, so the description must compensate. It explains 'resolution' (listing valid values) and 'last' (number of periods). However, 'home_id' is not mentioned, leaving its purpose unclear. The description adds value for two of three parameters, but the omission of home_id reduces the score.

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 clearly states the tool retrieves historical consumption data per period, including specific metrics (kWh, costs in EUR, average price). It uses a specific verb ('get') and resource ('consumption'). The mention of 'resolution' and 'last' further clarifies the scope, distinguishing it from sibling tools like get_consumption_report which likely provides aggregated reports.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools like get_live_measurement, get_price_forecast, and get_consumption_report exist, but the description does not explain when to prefer this one. The agent is left to infer usage from the name and parameters alone.

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