get_energy_prices

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds the pricing focus but does not disclose additional traits like response format or rate limits. With annotations present, the description meets the baseline but doesn't exceed it.

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 concise sentences: first covers purpose and scope, second gives usage boundaries. Every word earns its place; no redundancy.

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 3 optional parameters and no output schema, the description covers scope, data types, and exclusions. It does not describe the response format, but the pricing focus and ISO list provide sufficient context for an AI agent to use the tool accurately.

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 has 3 parameters (iso, state, data_type) with 0% description coverage. The description adds context about ISOs and data types but does not map them explicitly to parameters, especially 'state' gets no mention. It partially compensates but leaves gaps.

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?

Description clearly states the tool retrieves energy pricing data across 10 specific ISOs, listing data types (retail rates, natural gas, real-time grid status). It explicitly distinguishes from sibling tools get_grid_data and get_grid_intelligence by stating its pricing focus and what not to use it for.

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?

Provides explicit when-to-use (pricing) and when-not-to-use (fuel mix, demand, grid headroom) with direct references to alternative tools. This gives clear guidance for the AI agent.

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