rightmove_student_search

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

With no annotations, the description carries the behavioral disclosure burden. It correctly indicates a read-only search and adds the useful price-unit caveat ('Prices are monthly rents in whole GBP units'). However, it does not disclose pagination behavior, result ordering, or what happens when filters are combined, so transparency is partial.

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 and front-loaded with the essential purpose, then expands on filters and price units. The only mildly redundant piece is the repeated 'Search Rightmove's student-accommodation' in the second sentence, but overall every sentence serves a distinct purpose.

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?

The tool has 7 parameters and no output schema, yet the description does not describe the return format. It also relies on the schema to communicate that 'location' must come from autocomplete, a dependency that would be more discoverable if stated textually. Adequate but with obvious gaps.

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%, so the baseline is 3. The description's mention of price, bedrooms, and furnishing filters adds negligible meaning beyond the already-detailed parameter descriptions, though the 'whole GBP units' note reinforces the existing schema text.

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 opens with 'Search Rightmove student accommodation' and reiterates 'Search Rightmove's student-accommodation listings for a location...' The verb+resource is explicit, and the student-accommodation focus distinguishes this from siblings like rightmove_search, rightmove_commercial_search, and rightmove_new_homes_search by niche.

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?

It clearly implies use for student-accommodation searches and mentions the filter dimensions (rent, bedrooms, furnishing), but it never explicitly tells the agent when to choose this over the general rightmove_search or other search variants, nor does it mention the rightmove_autocomplete prerequisite for the location parameter. Usage is implied, not prescribed.

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