Find comparables

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

With no annotations, the description carries the burden. It discloses the data source (Land Registry), recency, proximity, and matching criteria. However, it does not describe output format, edge cases (e.g., no matches), or any side effects/security concerns.

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 concise sentence that front-loads the key information. Every word contributes to understanding the tool's purpose.

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 5 parameters, no annotations, and no output schema, the description is incomplete. It gives a high-level concept but leaves out parameter details, input usage, return structure, and potential limitations.

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 0%, so the description must explain parameters. It only vaguely maps 'recent' to monthsBack and 'nearby' to radiusMiles, but does not define each parameter or the input fields (uprn, address, postcode). It also references property type, size, and bedroom count, which are not input parameters, adding ambiguity.

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 specifies the tool's purpose: retrieving recent nearby Land Registry sales matched on property type, size, and bedroom count. It distinguishes from sibling tools like search_listings or compare_listings by focusing on surveyor comparables.

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 implies usage context (for surveyors seeking comparables) but does not explicitly state when to use it vs. alternatives like search_listings or compare_listings. No exclusions or alternative references are provided.

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