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

With no annotations, the description carries behavioral burden well by listing returned fields and noting sold mode via soldMode parameter. However, it omits potential rate limits, data freshness, and geographic scope (US only).

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?

Two concise sentences front-load the core action and return data, with no wasted words.

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 no output schema, the description adequately lists return fields and key parameters. Missing details on pagination or error handling, but still sufficient for a straightforward 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?

Schema coverage is 100%, so the description adds marginal value beyond schema. It restates 'city or ZIP' and 'for-sale or sold' but does not deepen understanding of minBeds, maxPrice, etc.

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 Realtor.com for-sale or sold listings by city or ZIP, specifies returned fields (price, beds, baths, etc.), and distinguishes from siblings like search_zillow and search_redfin by targeting Realtor.com.

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 indicates usage via city/ZIP and mentions 'No MLS login' for ease, but does not explicitly advise when to choose this tool over siblings (e.g., search_zillow) or provide exclusion criteria.

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