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

Annotations already declare readOnly/openWorld/idempotent and non-destructive, and the description adds meaningful context: no auth required, Open Government Licence, source data provider, and a promise of the same per-sale fields as by_postcode. No behavioral contradiction exists.

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?

Three dense sentences cover purpose, required-filter constraints, optional filters, pagination, return-field relationship, data source, auth, and licence with no filler. The core action and key constraint are front-loaded.

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 9-parameter tool with an output schema and rich read-only annotations, the description covers the essential runtime requirement (at least one area), all filter categories, pagination, auth, and licensing. No decision-critical information for invoking it correctly is missing.

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 description coverage is 100%, so the baseline is 3; the description mostly restates schema facts (GBP, YYYY-MM-DD, pagination) with illustrative values. It adds value mainly through examples like town="WARRINGTON" and county="GREATER LONDON", but the schema already documents each parameter.

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 opens with an explicit verb+resource ('Search HM Land Registry Price Paid Data') and scopes it to town, county, and district searches with concrete value examples. It also distinguishes itself by referencing sibling search_by_postcode, so an agent can tell this is the area-based variant.

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?

Clear context for when to use is provided: search by town, county, and/or local authority district, with at least one required and optional price/date filters. It does not explicitly say 'use search_by_postcode when you have a postcode' or name other exclusions, so it falls just short of a 5.

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