Free-text suggestion search across MLS feeds

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds value by revealing the endpoint behavior (bypassing groups, hitting global endpoint) and listing returned fields (id, address parts, beds/baths, price, thumbnail). No contradictions with 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 paragraph of four sentences. It front-loads the core action, then adds context, return info, and optional parameter guidance. Every sentence contributes meaningful information without redundancy.

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 the tool's simplicity (2 parameters, no output schema), the description covers purpose, usage, return shape, and parameter hints. It could mention result limits or pagination, but overall it provides sufficient context 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 0%, so the description carries full burden. It explains the 'query' parameter accepts addresses, MLS numbers, or partial queries, and 'group_id' scopes to a market. While query format specifics are omitted, the description provides meaningful usage context beyond the bare 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 clearly states it performs a 'cross-feed suggestion search by address, MLS number, or partial query,' and distinguishes itself from siblings by noting it bypasses group/saved-search structures and hits a global endpoint. The verb 'search' combined with specific resource details makes the purpose unambiguous.

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 explicitly marks it as 'useful for' address lookups or MLS number searches, and mentions scoping via optional group_id. However, it does not explicitly state when not to use it or name alternative tools for different use cases, leaving some ambiguity for an AI agent.

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