Get nearby homes.com listings for a property

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint, and the description adds valuable non-obvious behavior: the nearby section is a curated cross-link list, not a comparable-sales set, and only URL + address are exposed (no price/beds/baths/sqft/photo). This prevents incorrect assumptions about the data.

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 concise despite covering purpose, parameters, output shape, caveats, and follow-up guidance. It front-loads the core operation, then layers details logically, with no redundant or filler sentences.

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?

There is no output schema, so the description correctly provides the full return shape: { property_id, url, count, listings: [...] }. It also covers important limitations and the enrichment path, making it complete enough for an agent to select and invoke the tool correctly.

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 baseline is 3. The description adds a little semantic context, such as url being 'the property whose neighborhood to inspect' and the default For Sale tab behavior, but limit and include_rentals mostly restate the schema descriptions.

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 states a specific verb ('Scrape ... and return'), a precise resource (the nearby-links section of a homes.com detail page), and the expected output (nearby active listings). It clearly distinguishes this tool from siblings like homes_get_property and homes_search_properties by focusing on the curated nearby cross-link list.

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 clear context: it is for inspecting the nearby-links section of a given property page, with defaults and optional flags explained. It also explicitly points to homes_get_property for enriching rows, which is a helpful alternative cue, though it does not list explicit 'when not to use' scenarios.

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