get_energy_prices

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

Annotations already indicate readOnlyHint=true, so the description does not need to restate that. It adds value by specifying the data focus (pricing, not fuel mix/demand) and listing the ISOs. No contradiction and no missing behavioral information for a read-only tool.

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 with no unnecessary words. It front-loads the core purpose and follows with exclusion guidance, making it easy to parse quickly.

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 provides good high-level context, given there are 3 parameters with no schema descriptions and no output schema, more detail on how to use the parameters (e.g., required combinations, default behavior) would improve completeness. The tool is simple but the description leaves some gaps.

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% with no parameter descriptions. The description lists the 7 ISOs and data types (retail rates, natural gas, real-time grid status), which hints at possible values for 'iso' and 'data_type', but does not directly map to parameters or explain the 'state' parameter. This provides some guidance but leaves ambiguity.

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 provides energy pricing for 7 specific US ISOs, listing them and the types of data (retail rates, natural gas, real-time grid status). It also explicitly distinguishes from siblings by naming alternative tools for other use cases, making the purpose unambiguous.

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 explicit when-not-to-use guidance ('do NOT use for fuel mix, demand or grid headroom') and names the correct alternative tools ('use get_grid_data or get_grid_intelligence'), giving clear direction for appropriate usage.

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