Search US Properties For Sale

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

Annotations already provide read-only (readOnlyHint=true), non-destructive (destructiveHint=false), and idempotent (idempotentHint=true) hints. The description adds valuable context about data source ('Millions of MLS listings (RapidAPI / Realtor.com data)'), which helps set expectations without contradicting any 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 single, well-structured sentence that front-loads the action and lists key filters and return data. It is concise yet informative, though it could be slightly more structured with bullet points for readability.

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?

Given that an output schema exists, the description's mention of return fields (address, price, specs, photos) is sufficient. Annotations are present, and the parameter schema covers pagination. No critical missing context, though a brief note on default sorting or pagination behavior would slightly improve completeness.

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?

With 100% schema coverage, each parameter already has a description. The tool description adds extra semantic guidance (e.g., 'use with state_code' for city, 'alternative to city+state' for postal_code), enhancing understanding beyond the raw schema.

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 uses a specific verb ('Search') and specifies the resource ('active for-sale property listings across the US'). It enumerates filter criteria and return fields, clearly distinguishing it from sibling tools like realestate.location.suggest or realestate.property.details.

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 clearly indicates the tool's scope (US properties for sale) and provides filter hints like 'use with state_code' and 'alternative to city+state'. However, it does not explicitly state when not to use this tool or mention alternative tools, missing some side-by-side guidance.

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