rightmove_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the search action and does not explain key behaviors such as the required autocomplete location identifier, status values, pagination behavior, or result format.

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 short but redundant: 'Search Rightmove properties' and 'Search for properties on Rightmove' say essentially the same thing. It lacks front-loaded unique information and earns no structural credit beyond being minimal.

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 tool with 10 parameters, one required parameter, no output schema, and no annotations, this description is too thin. It omits the autocomplete prerequisite for location, available status values, property type constraints, and any sense of what the search returns, leaving important context to the schema.

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 parameters are already well documented at the schema level. The description's mention of 'location, price, bedrooms' merely echoes the parameter names and adds no additional semantic value.

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?

"Search Rightmove properties" names a clear verb and resource, and the filter mention adds scope. However, it does not differentiate from sibling searches like rightmove_commercial_search or rightmove_new_homes_search, so it falls short of a 5.

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 gives no guidance on when to choose this tool over rightmove_commercial_search, rightmove_new_homes_search, or rightmove_student_search. It also does not mention that location should come from rightmove_autocomplete, so the agent must infer the usage context from the schema alone.

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