Search all pages

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses meaningful operational behavior: 60 listings per page, ~4s polite request per uncached page, a 5-page cap, and deduplication. These details help the agent anticipate cost, latency, and output semantics without guessing.

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 sentences deliver the core behavior, constraints, and usage guidance with no filler. The most important operational facts are front-loaded.

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 output schema exists, the readOnly/openWorld annotations cover safety, and the sibling list is available, the description supplies the essential selection and invocation context: exhaustive aggregation, deduplication, paging behavior, and when to choose search_listings instead. No critical gap remains for an agent deciding to call it.

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%, so the description does not need to compensate heavily. It adds significant meaning for maxPages by explaining page size, request pacing, and the 5-page cap, which goes beyond the schema's bare default/max fields. Other parameters remain adequately covered by their names/types and the few existing schema descriptions.

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 states a specific action ('Aggregate multiple result pages into one deduplicated list') and clearly identifies the resource (result pages/listings). It also differentiates from search_listings by framing search_all for exhaustive scans, so an agent can distinguish it from the main sibling without opening the schema.

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 for exhaustive scans; prefer search_listings for quick looks,' which gives both a positive condition and a clear alternative. This directly answers when to choose this tool versus the most relevant sibling.

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