Grid Transition Radar

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds meaningful context beyond annotations by disclosing that a paid key is required for the transition thesis component, and by describing the output composition. It does not mention rate limits or pagination, but that is not critical given the 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 three sentences and front-loaded with purpose, then outputs, paid-key caveat, and exclusions. Each sentence contributes useful information without redundancy, though it is slightly longer than necessary.

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 the output schema and annotations, the description supplies sufficient context: explains what the emergence signal includes, mentions the paid tier, provides an example, and names alternatives. It could detail the ISO rollup more, but overall it is complete for an agent to decide when to invoke this tool.

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 100% with both parameters (limit, max_months) having descriptions. The description adds context by referencing max_months in the example and tying it to 'time-to-power', but limit is left to schema. This is modest added value, so baseline 3 is appropriate.

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 states it is a forward-looking radar for emerging hyperscale-friendly grids, specifying exact outputs: US markets+ISOs with BUILD verdict, excess-power headroom, short time-to-power, an ISO rollup, and a grid-headroom leaderboard. It explicitly contrasts with retrospective reports and distinguishes from sibling tools like get_interconnection_queue and rank_markets.

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 forward-looking emergence radar, and when not to use: not for current ISO queue snapshot (use get_interconnection_queue) or present-day market ranking (use rank_markets). Also provides a concrete example query (max_months=24), giving clear guidance.

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