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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is low. The description usefully adds that the response is a summary with a link to the full overview, clarifying the scope of what is returned without explaining pagination or empty-result behavior.

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, no filler: the first front-loads the usage trigger, the second states the return. Every clause earns its place.

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?

For a single-parameter, read-only tool with full annotations and an output schema, the description covers what is needed to call it. The only minor gap is how it behaves when no overview exists for a place or when the name is ambiguous.

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 documents 'place' as 'Town, village or neighbourhood name.' The description adds a real constraint the schema lacks: the geographic scope is UK-only, and the accepted place types are implied by the trigger sentence, so it contributes meaning beyond the schema.

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 (MyPorta's Area Overview for a UK town/village/neighbourhood) and what it returns (a summary plus a link to the full overview). The area-vs-home resource distinction separates it cleanly from siblings compare_homes, get_home and search_homes, though it never names them.

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?

It gives an explicit, concrete trigger: 'Use this when the user asks what a UK town, village or neighbourhood is like to live in.' That is a clear use condition, but it offers no exclusions or pointers to alternative tools (e.g. what to call for individual home data).

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