Bulk-fetch OneHome listings by id

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

Annotations already mark readOnlyHint, openWorldHint, and idempotentHint, and the description builds on them with valuable behavioral details: concurrent fan-out capped at 6, one retry per row for bridge timeouts, per-row error isolation, automatic extracted_features population, and description omission by default. It gives the agent a clear execution model 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 dense but every sentence carries operational meaning, and the primary purpose is front-loaded in the first sentence. It covers behavior, errors, defaults, concurrency, and comparisons without filler or repetition.

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 fully explains the return shape: each row is either { listing_id, property } or { listing_id, error }. It also covers failure isolation, concurrency, retries, defaults, and optional output fields, so the agent has everything needed to invoke and interpret results 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 50%, and the description compensates for include_description and group_id by explaining their defaults and effects. listing_ids constraints are in the schema, so less description is needed there. However, saved_search_id is not described in either the schema or the description, leaving a meaningful parameter unexplained.

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 OneHome listings in a single call.' It clearly distinguishes this tool from the sibling onehome_compare_properties by noting it returns rows rather than a side-by-side summary table. No ambiguity remains about what the tool does.

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 gives clear context for when to use this tool (bulk fetching by id) and explicitly routes summary-table needs to onehome_compare_properties. It also tells the agent that batch-to-batch work should be split, and that single bad ids are handled per row. It does not explicitly contrast with the singular onehome_get_property, so a small exclusion gap remains.

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