Bulk-resolve street addresses to Redfin URLs + home_ids

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

The description goes well beyond the annotations by detailing output order preservation, unresolved entry behavior ('resolved: false'), distinct retryable statuses (timeout/bridge_down/pending), per-row retry-once-on-timeout, server-side concurrency ~6, and a hard deadline. This provides rich behavioral context that annotations alone (readOnlyHint, openWorldHint, idempotentHint) do not cover.

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 front-loaded with the main purpose and then details in a logical order. Every sentence adds value, but it is slightly longer than necessary. However, the additional detail on error handling and use case justifies the length, making it well-structured and informative.

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 has a single parameter, no output schema, and annotations covering idempotency and read-only, the description is fully self-contained. It explains input format, output behavior, error handling, retry logic, concurrency, and use cases, leaving no gaps for an AI agent to 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?

The input schema already provides 100% coverage with a clear description of the 'addresses' parameter as an array of strings or objects. The description adds minimal extra meaning beyond restating the schema, so it meets the baseline for high schema coverage without significantly enhancing parameter understanding.

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 the tool's purpose: bulk-resolve street addresses to Redfin URLs and home_ids. It distinguishes from siblings by noting it collapses multiple search calls into one trip, and the title includes 'Bulk-resolve' which differentiates it from single-address tools like redfin_get_by_address.

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 says 'Use this when you have a list of properties from another system... and need their Redfin handles for follow-on calls.' It also contrasts with the typical multi-call flow. However, it does not explicitly state when not to use it or name alternatives, though the context implies it's for batch processing.

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