get_grid_intelligence

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

Annotations set readOnlyHint=true, and description adds behavioral detail: returns specific JSON fields, notes that balancing authorities return live generation mix but other data remains ISO-level. No contradiction; adds context beyond 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?

Description is relatively long but front-loaded with use case and example. Every sentence adds value (parameter details, sibling distinctions, partial output schema). Could be slightly more concise but still effective.

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 3 params, no output schema, no enum definitions, description covers core use case, parameter semantics, return fields list, and exclusions. Does not explain each return field in depth, but adequate for agent invocation.

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?

Input schema has 3 undocumented string parameters (0% coverage). Description compensates fully: explains region_id accepts aliases (iso/region), lists exact enum values (7 ISOs and many balancing authorities with examples), and clarifies behavior for different values.

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?

Clearly states the tool provides a grid-headroom and interconnection-queue brief for one ISO. Gives specific verb+resource: 'get grid intelligence for one region'. Distinguishes from siblings like compare_isos and get_grid_scoreboard.

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 says when to use (user asks about power capacity for a specific ISO/balancing authority) and when not to (comparing ISOs or global ranking), with clear alternatives (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.