get_grid_connection_intelligence

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses key logic: NESO boundary matching, fallback to nearest GSP, and conditional addition of SSEN/NGED data. It also includes a critical disclaimer ('Not a connection offer or capacity guarantee'). It could mention return format or rate limits, but for a read-only aggregation tool, this is strong.

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 dense sentence that front-loads the tool's purpose and efficiently packs multiple clauses about data sources and conditions. While it could benefit from bullet points, it contains no filler and earns its length.

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?

This is a complex aggregation tool with no output schema. The description explains the resolution logic, fallback behavior, data sources, and limitations, providing substantial context. It doesn't describe the return structure or possible empty results, but overall it covers key aspects adequately.

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?

The input schema has 100% coverage with descriptions for all four parameters. The description adds no extra parameter-level detail beyond the schema. Baseline 3 applies because the schema already handles parameter semantics.

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 what the tool does: it resolves a GSP region, falls back to the nearest GSP, and aggregates grid connection context (TEC register, substations, SSEN headroom, NGED queue). This is a specific verb+resource description that distinguishes it from sibling tools specializing in individual data sources.

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 clearly implies usage for GB grid connection assessment with 'GB grid connection intelligence' and conditional data coverage. However, it doesn't explicitly state when to use this tool vs alternatives, nor does it provide exclusions or reference the sibling tools that offer more focused data.

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