Bulk-fetch Zillow properties by zpid

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

Even though annotations already declare readOnlyHint and idempotentHint, the description adds substantial behavior: per-row success/error isolation, retry-once-on-timeout, concurrency cap of 6, bot-wall handling with exponential backoff, error_kind values like bot_challenge and pending, a blocked/retry_after_s envelope, and an overall hard deadline. This goes far beyond the 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 front-loaded with purpose and the alternative tool, but the rest is one dense paragraph packed with implementation specifics, issue references (#78, #90, #98), and jargon like 'SW evictions' and 'burst 20'. The content is valuable, but the structure is not concise or easily scannable; bullet points would improve it.

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?

With no output schema, the description takes on the burden of explaining return values—and it does cover the per-row shapes, error kinds, bot-challenge envelope, and pending count. The main gap is that the success `property` object's fields are left unspecified, though the description is otherwise remarkably complete for a complex bulk endpoint.

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 'one structured row per input id' and explains that a bad zpid does not fail the whole call, but it does not define exact URL/path formats or clarify how zpids and urls relate beyond what the schema already says. The schema carries most of the parameter meaning.

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 opens with a specific verb and resource: 'Fetch up to 200 Zillow property records in a single call' and clearly frames it as the bulk endpoint. It also distinguishes itself from zillow_compare_properties by stating there is no pivoted side-by-side summary table, so an agent can tell them apart.

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 routes to an alternative: 'for 2-25 listings with a comparison summary use zillow_compare_properties'. This is a clear when-to-use-this-versus-that signal, which is exactly what an agent needs for tool selection.

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