Search Products

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds useful behavioral context about session and slot sensitivity of results, which is beyond the annotations. No contradictions detected.

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 concise: two sentences with no wasted words. The first sentence states the core function, and the second adds important context. It is front-loaded and efficient.

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 tool has 3 parameters and no output schema, the description covers the main purpose and context sensitivity but omits details about pagination, result format, and what 'current session context' means precisely. It is minimally viable for a search tool but leaves some gaps.

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 0%, meaning the schema provides no parameter descriptions. The tool description does not mention any parameters either, forcing the agent to rely solely on the schema's property names. For a 3-parameter tool, the description should have added meaning (e.g., that 'query' is a text string, 'pageSize' limits results, 'pageToken' handles pagination), but it fails to do so.

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 Voila products by text query for the current session context. It uses a specific verb and resource, and the phrase 'by text query' distinguishes it from sibling tools like voila_get_category_products or voila_get_discounted_products.

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 explicit guidance: 'Product availability and pricing are session and slot-context sensitive, so prefer checking slots first when planning an order.' This tells the agent when to use the tool and suggests a contextual alternative (checking slots), though it does not explicitly name the sibling tool voila_get_slot_listings.

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