get_grid_intelligence

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

Annotations already declare readOnlyHint=true, so non-destructive behavior is signaled. The description adds value by outlining the return shape and stating the tool operates on a single ISO, which conveys safe, idempotent behavior without disclosing rate limits or auth specifics.

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 a single paragraph but front-loads the use case, follows with example, parameter info, return fields, and exclusions. Every sentence adds value, though the parameter aliases could be more structured.

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 moderate complexity (3 params, no output schema), the description covers purpose, usage, parameters, returns, and exclusions. It does not explain what happens with multiple parameters or the meaning of constraint_score, but the listed return fields provide sufficient context.

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%, but the description provides guidance: it indicates region_id as the primary parameter, lists accepted aliases, enumerates valid values, and includes an example. This compensates significantly for the bare schema, though it doesn't explain the role of iso and region parameters.

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 explicitly states the verb-resource pair ('get grid-headroom + interconnection-queue brief') and ties it to a specific user query. It distinguishes this tool from siblings by naming alternatives for multi-ISO comparison and global ranking.

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 includes a clear 'Use when' clause with a concrete example, and explicitly states two negative cases ('Do NOT use...') with references to sibling tools (compare_isos, get_grid_scoreboard).

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