search_property_listings

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

With no annotations, the description provides key behavioral context: it returns historical and current data from a specific source, includes a marker for live status, and lists the output fields. It does not mention error handling, rate limits, or authorization, but for a read-only search tool, the disclosure is sufficient.

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 two sentences with no extraneous information. It front-loads the action ('Find live and historic sales/lettings listings') and efficiently lists the return fields and source. Every sentence serves a 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?

Given the tool's simplicity (one parameter, output schema present), the description covers purpose, input, output, and data source. It lacks explicit usage guidance and differentiation from siblings, but overall it is nearly complete for an agent to understand and invoke the tool.

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 only parameter, 'uprn', is described in the schema as 'Unique Property Reference Number.' The description does not add additional semantic context beyond what the schema provides. Since schema coverage is 100%, a score of 3 is appropriate.

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 the tool's purpose: finding live and historic sales/lettings listings linked to a UPRN. It specifies the returned fields (asking price, status, agent details, etc.) and the data source (Home.co.uk's panel of portal partners with 30+ years of data). This distinguishes it from sibling tools like 'get_property_sales' or 'lookup_property' which may focus on specific aspects.

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 implicitly suggests use when you need both sales and lettings listings for a UPRN, but it does not explicitly state when to use this tool versus alternatives like 'get_property_sales' or 'get_comparables'. No exclusions or prerequisites are mentioned.

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