vt_search_products

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's minimal behavioral detail (returns summaries) adds limited value beyond annotations. There is no contradiction. The description could mention pagination or default sorting, but it is adequate.

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 two short sentences, front-loading the core action and result, then referencing auxiliary tools. Every sentence earns its place, no unnecessary words. Appropriate for the parameter count.

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 high parameter count (18) and no output schema, the description covers essential aspects: what the tool does, what it returns, and how to prepare inputs. However, it omits mention of pagination defaults (start=1, count=10) and sort default (DEFAULT). Still fairly complete for a search tool with openWorldHint.

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 coverage is 100% with descriptions for all 18 parameters. The description adds value by grouping filter categories (destination, tags, price, dates, rating, duration), which helps understand the parameter space concisely. This goes beyond simple schema repetition.

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 the tool searches Viator tours, activities, and experiences with structured filters, and returns product summaries with pricing and booking URLs. It distinguishes from sibling tools like vt_search_freetext and vt_search_attractions by specifying structured filters.

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 advises using vt_list_destinations and vt_list_product_tags to find IDs, providing clear prerequisite guidance. It implies usage for structured search vs. free-text or attractions search, but does not explicitly state when not to use this tool.

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