WB Catalog Search

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds significant context beyond that: it explains the two-stage process (ID search then enrichment), error semantics (BadRequestError, RateLimitedError, TransportDownError), and that transport failures degrade to no_results. This is substantial behavioral disclosure.

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 well-structured with headers for purpose, return format, and error format. Each sentence earns its place, and it is front-loaded with a one-sentence summary. No fluff or redundancy.

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?

This search tool has a two-step implementation, pagination, and distinct response/error types. The description covers purpose, implementation details, return format (including the no-results case), and error behavior. It is complete for the tool's complexity, especially with output schema and annotations present.

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%, and each parameter (dest, page, query) already has a clear description in the schema. The tool description does not add new parameter semantics, so baseline 3 is appropriate given that the schema does the heavy lifting.

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 'Search WB catalog by text query' with a specific verb and resource, and distinguishes itself from siblings like wb_card (product detail) and wb_category_products (category navigation). The mention of using a lightweight endpoint and enriching via wb_card reinforces its unique role.

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 provides clear usage context for text searching the WB catalog, including pagination behavior and no-results handling. However, it does not explicitly name alternatives or state when not to use the tool, unlike the calibration example that names search_calls_extensive.

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