get_energy_prices

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

The annotations already declare readOnlyHint=true and destructiveHint=false, establishing a safe read operation. The description adds valuable behavioral context by stating the tool returns 'historical' data, which goes beyond the schema and clarifies the temporal scope. No contradictions with annotations.

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 a single, concise sentence that is front-loaded with the verb and resource. Every word adds value, with no redundancy or filler.

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?

The tool is simple with one optional parameter, no required parameters, and no output schema. The description combined with annotations gives a sufficient understanding of what the tool does and its safety profile. However, it does not elaborate on the return format or time range, which would make it fully complete, but given the low complexity, this is adequate.

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 input schema has 100% coverage for the single optional parameter 'network', with its own description. The tool description adds no additional parameter semantics, so the baseline of 3 applies as the schema already documents the parameter fully.

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 uses a specific verb 'Query' and a specific resource 'historical energy unit price on the TRON network', clearly distinguishing it from similar siblings like get_bandwidth_prices. The inclusion of 'historical' further differentiates it from estimate_energy, which is forward-looking.

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 implies when to use it (when needing historical energy prices) but provides no explicit guidance on when not to use it or what alternatives exist. It does not mention related tools like get_bandwidth_prices or estimate_energy, leaving usage context to be inferred from the tool name and siblings.

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