Retrieve detailed Rightmove property details by ID. Get structured listing information in JSON for a specific property.
Get Rightmove property details. Returns detailed information for a specific Rightmove property by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Rightmove property ID |
Changes observed during successful MCP inspections.
v1.16.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must disclose behavioral traits. It only says 'Returns detailed information' but does not mention side effects (likely read-only), authentication needs, error handling, or any other behavioral context. This is insufficient for a tool with no structured annotations.
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 concise two-sentence statement with no filler. It front-loads the verb and resource, making it easy to parse quickly.
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 no output schema, the description should clarify what 'detailed information' includes. It is vague about the return structure or content, leaving the agent without expectations. Given the tool's simplicity (single parameter) and lack of output schema, the description is incomplete.
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 coverage is 100% and the id parameter already has a clear description in the schema. The description adds no extra meaning beyond what the schema provides, so a baseline 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 verb 'Get' and the resource 'Rightmove property details', specifying it operates by ID. It distinguishes itself from sibling tools like search and autocomplete, making the purpose unambiguous.
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?
No guidance is given on when to use this tool versus alternatives, such as rightmove_search to obtain the ID first, or other rightmove tools. The description assumes the user already has a property ID without explaining the workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.