grid_transition_radar

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

Annotations indicate readOnlyHint=true, consistent with a read-only tool. The description adds useful context: it's predictive, returns specific outputs, and requires a paid key for additional thesis. No contradictions, though no mention of rate limits or auth beyond key.

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 somewhat lengthy but front-loaded with the core purpose. It uses clear sentences and includes a sample usage. Could be slightly more concise, but structured effectively.

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?

No output schema exists, so the description carries full burden for explaining return values. It details outputs (BUILD verdict, headroom, time-to-power, ISO rollup, leaderboard, transition thesis) and clarifies what the tool does not do. Fairly complete for the complexity.

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 suggests trying max_months=24, giving a usage hint, but does not explain the meaning or valid ranges for 'limit' or 'max_months'. Some value added but incomplete.

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 it's a forward-looking radar for emerging hyperscale-friendly grids, with specific outputs like BUILD verdict, excess power headroom, and short time-to-power. It distinguishes itself from retrospective reports and 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 (forward-looking emergence) and when not to (current ISO queue snapshot or present-day market ranking), with specific alternative tool names provided. The description also suggests a sample usage 'grid_transition_radar max_months=24'.

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