Batch DNS product search

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 meaningful behavioral context beyond annotations: a shared browser session, the SESSION_DROP risk from parallel calls, and the per-result layout (query, count, items with stock enum).

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?

Three tight sentences, with the most important usage guidance front-loaded. Every sentence adds value: what it does, when to use it, and what the result blocks look like.

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?

There is no output schema, so the description carries the burden of explaining return shape, but it only sketches 'query, count, items with stock enum'. Given 9 parameters and low schema coverage, an agent would benefit from more detail about filtering, sorting, pagination, and item fields before confidently using the full capability.

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 only 44%, and the description does not compensate for the undocumented parameters (page, sort, inStock, priceMax, priceMin). It mentions the 1–10 query range but provides no additional semantics for the filtering, sorting, or pagination parameters.

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 identifies the action ('run 1–10 search queries in one call') and resource ('DNS product search'), and differentiates it from the single-query sibling dns_search by emphasizing batch behavior. The title and first sentence together leave no ambiguity about what this 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?

Explicitly states when it is preferred ('PC builds / price scans') and why it beats the alternative ('Avoids parallel dns_search bursts that cause SESSION_DROP'). This gives the agent concrete routing guidance and names the sibling it protects against.

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