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

Annotations already declare readOnly, idempotent, non-destructive, non-open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond them: partial inputs (district/sector) return only councils, and NI coverage is absent. Return format/pagination is not mentioned, but the tool is a simple lookup.

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?

Two sentences with no filler, front-loaded with what the tool returns and followed by input-form and coverage caveats. Every clause carries information.

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?

With no output schema, the description compensates by describing the returned areas and their codes/pages, plus the geographic coverage limit. It is complete for a one-parameter lookup, though it never says what an invalid or unknown postcode yields.

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% and the single parameter's description already enumerates full postcode, sector and district formats. The description's restatement of E8 / E8 1 formats largely duplicates the schema, adding little beyond the output-oriented framing.

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 a specific resource (the areas a GB postcode sits in, with codes and pages) and enumerates the area types returned, so an agent can tell what it produces. It does not name or contrast with any sibling (get_place, search_places, fetch), so the differentiation is left to inference.

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?

Usage is implied by the input-form guidance (district, sector, full postcode) and one explicit exclusion ('Northern Ireland postcodes are not available'), which functions as a when-not. There is no guidance on when to choose this over get_place or search_places for geographic lookups.

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