rightmove_commercial_search

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

With no annotations provided, this description is the only source of behavioral disclosure. It adds a meaningful nuance: for to-let listings, the price amount follows the listing's own frequency (monthly or yearly), which clarifies price semantics. However, it does not mention pagination, required prerequisites, or response characteristics, leaving some behavior unaddressed.

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 consists of only two sentences and front-loads the purpose with the verb 'search'. There is a slight redundancy between the first and second sentences, but the description is overall tight and does not waste words.

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 has 8 parameters, no output schema, and no annotations, the description covers the core search behavior and filtering but omits practical context such as how to obtain the location identifier or what the result structure looks like. It is enough to infer a search but could be more complete for invocation.

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 input schema already covers all parameters (100% coverage), so the baseline is 3. The description adds value by specifying what the price, floor area, and property-type filters mean, and explicitly notes the squ ft unit and the frequency semantics for to-let listings. This goes beyond the schema's basic descriptions.

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: to search Rightmove commercial property listings for sale or to let, with filters. It uses a specific verb ('search') and resource, and the phrase 'commercial property' distinguishes it from sibling residential or new-home search tools. The scope is evident.

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 usage is implied by the word 'commercial' and the content, but there is no explicit comparison to alternatives such as rightmove_search or rightmove_new_homes_search. No exclusion or when not to use is stated, so the guidance is implicit rather than explicit.

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