rightmove_student_search

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

No annotations are provided, so the description must disclose behavioral traits. It mentions that prices are monthly in whole GBP, which is helpful, but it does not state that this is a read-only operation, what the return format looks like, whether pagination is supported, or any side effects. For a search tool with no annotations, this is a significant gap in behavioral transparency.

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 three sentences. The first sentence 'Search Rightmove student accommodation' is redundant with the tool name and adds little value. The second sentence provides useful detail about filters, and the third clarifies price units. While overall short, the redundant opening wastes a sentence, so it is not maximally concise.

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 explain what the tool returns (e.g., a list of student accommodation properties). It does not mention return format, pagination, or any limitations. The schema is comprehensive for inputs, but the lack of output information means an agent cannot fully anticipate the tool's behavior, making it incomplete for a search 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 input schema covers all 7 parameters with descriptions, achieving 100% coverage. The description adds minimal extra meaning, only reiterating that prices are monthly in whole GBP, which is already stated in the schema for max_price and min_price. It does not clarify the location identifier format beyond what the schema provides. Baseline of 3 is appropriate since schema carries the load.

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 it searches Rightmove's student-accommodation listings, with specific verb 'Search' and resource 'student-accommodation listings'. It also mentions filters for rent, bedrooms, and furnishing. This distinguishes it from other rightmove tools like rightmove_search, rightmove_new_homes_search, and rightmove_commercial_search by explicitly targeting student accommodation.

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 implies usage for student accommodation searches by the title and content, but it does not explicitly mention alternatives or when not to use this tool. There is no guidance on choosing between this and other rightmove search tools (e.g., rightmove_search for general listings). The context signals are implied rather than stated.

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