shelly_energy_history

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

The description goes beyond the readOnlyHint annotation by disclosing that the data is 'best-effort' and that detailed historical queries require local backends. This informs the agent about potential incompleteness and the tool's bounded reliability over cloud.

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 two sentences, concise and front-loaded. The first sentence covers purpose and a key limitation. The second adds technical detail but could be streamlined for clarity.

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 description covers output behavior and limitations, it fails to explain input parameters. The presence of an output schema helps, but the lack of input explanation leaves a significant gap in completeness.

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?

With 0% parameter description coverage in the schema, the description should explain the parameters but does not. It omits what 'device' and 'channel' represent or how to specify them, leaving the agent without necessary input context.

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 it provides 'energy history' with 'lifetime totals' and 'per-minute series', distinguishing it from sibling tools like shelly_energy_live (live data) and shelly_get_status (current state). The verb 'retrieve' is implied and the resource is specific.

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 provides context on when to use the tool: 'over cloud only totals + recent by-minute are available' and notes that 'richer history needs a local connection'. It does not explicitly name alternatives, but gives clear limitations that guide usage.

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