get_grid_data

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

Description adds context beyond annotations by specifying 'raw real-time telemetry' and the exact ISOs covered. Annotations already provide readOnlyHint, so the bar is lower. However, it does not disclose latency, caching behavior, or data availability, which could be improved.

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 sentences: first covers data and scope, second adds usage boundaries. No verbose or redundant phrasing. Front-loaded with purpose.

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?

Covers purpose and exclusions well, but lacks details on parameter usage and output format. Without an output schema, the description could mention return type or examples. For an AI agent to invoke correctly, additional parameter guidance is needed.

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%, and the description does not explain the possible values for 'metric' or 'period'. It implies metric options from listed data types but lacks explicit mapping. The 'iso' parameter is partially explained via the list of ISOs, but no format or examples provided.

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 'Real-time electricity grid data' and lists specific ISOs and data types (fuel mix, demand, prices). It distinguishes from siblings by explicitly stating what not to use it for and directing to alternative tools.

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 provides when-to-use (real-time telemetry for one ISO) and when-not-to-use (power-availability, interconnection-queue, or retail/gas pricing) with references to specific alternative tools: get_grid_intelligence and get_energy_prices.

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