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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds a genuinely useful caveat that to-let price follows the listing's own frequency (monthly/yearly), but says nothing about pagination behavior, result caps, or return structure.

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?

Purpose is front-loaded and the to-let caveat is well placed, but the prose redundantly repeats parameter details already present in the schema (location's required-ness, the REGION^87490 example, the page default).

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 an output schema present, return values need not be explained, and annotations cover the safety profile, so the description only needs to convey purpose, filters, and routing. It does this adequately, though the sibling routing is thin across the several Rightmove search tools.

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 schema already documents all eight parameters fully. The description largely restates the schema (location identifier example, page default), with the only real added meaning being the to-let price-frequency note; baseline 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?

States a specific verb (search) and resource (Rightmove's commercial property listings) with scope (for sale or to let) and the filterable dimensions. It explicitly names the sibling rightmove_search, so an agent can tell it apart as the commercial-specific 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?

Provides a routing hint by naming rightmove_search as the general alternative, implying this tool is the commercial-specific channel. However, it does not state when-not-to-use or disambiguate against the other Rightmove siblings (new_homes, student), so the guidance is contextual but not exhaustive.

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