statistics_get_energy_statistics

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

No annotations provided, so description bears full burden. It discloses it is a read-only convenience wrapper that auto-discovers sum statistic IDs. However, it does not mention prerequisites (e.g., energy sensors configured), error conditions, or what happens if no sensors exist. The existence of an output schema partially rescues missing return format details.

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, no wasted words. The first sentence clearly states the primary purpose (verb+resource+scope), and the second adds valuable context (wrapper, auto-discovery, use case). Efficient and front-loaded.

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?

Given the tool has only two parameters and a sibling tool for generic statistics, the description covers the core purpose but misses details about the period parameter and prerequisites (e.g., need for configured energy sensors). The output schema exists but the description could still reference expected results.

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 coverage is 0% (no parameter descriptions in schema). The description explains 'days' implicitly via 'last N days' but does not explain the 'period' parameter at all. With 0% schema coverage, the description should have explained both parameters; it fails on period.

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 gets sum statistics for all energy-related sensors (kWh, gas m³) for the last N days. It also distinguishes itself as a convenience wrapper around get_statistics, differentiating from the generic sibling tool.

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 indicates it is a convenience wrapper around get_statistics and auto-discovers sum statistic IDs. It also mentions usefulness for EON energy consumption analysis, which implies when to use it. However, it lacks explicit guidance on when not to use it or when to prefer the generic get_statistics.

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