get_grid_data

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

Annotations already provide readOnlyHint=true, so no contradiction. The description adds context that it is 'raw real-time telemetry' for one ISO, indicating no destructive behavior. Could be improved by mentioning data freshness or rate limits, but overall good.

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 in a single paragraph but is dense with information. It could be broken into bullet points for clarity, but it remains concise without unnecessary words.

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?

With 3 parameters and no output schema, the description covers the tool's main purpose and usage guidelines well but lacks details on the 'metric' and 'period' parameters. It is adequate for use but not fully comprehensive.

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 description coverage is 0%, so the description must compensate. It explains the 'iso' parameter (pass one of the 7 ISOs) but does not document 'metric' or 'period' parameters. This leaves significant ambiguity for the agent.

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 real-time electricity grid data for 7 US ISOs, specifying fuel mix, demand, and 24h demand curve. It uses specific verbs and resources, and distinguishes itself from siblings by naming alternative tools for other analyses.

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?

Explicitly states when to use (for real-time data) and when not to use (power-availability, retail pricing) with direct references to alternative tools (get_grid_intelligence, get_energy_prices, get_grid_scoreboard). Also hints at passing iso parameter.

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