find_product

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

No annotations are provided, so the description must fully disclose behavior. It explains auto-detection of product category, routing to resolvers, and states which categories are live and which are rolling out. It lacks explicit details on authentication or rate limits, but for a non-destructive routing tool, this is reasonably transparent.

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 and well-structured, starting with the core purpose ('Smart router'), then detailing supported categories and usage guidance. Every sentence adds value without 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?

Given the tool's complexity (routing, multiple categories) and lack of output schema, the description adequately explains behavior, status, and when to use. It could mention fallback behavior for unsupported categories, but overall it is complete enough for an agent to use correctly.

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?

The input schema has 100% coverage with descriptions for both parameters. The description adds context by explaining the 'query' parameter with natural language examples and the 'category' enum with the 'auto' default. This exceeds the baseline of 3 by providing meaningful usage context.

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 explicitly states it is a 'Smart router' that finds the best place to stream, buy, or collect products. It specifies the product categories (music, games, etc.) and clearly distinguishes from sibling tools like discover_music, resolve_game, and resolve_music.

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: 'Use this when the query is ambiguous or when music could be streamed, purchased digitally, or found on physical media.' It also explains the category parameter's auto-detect behavior, helping the agent decide when to use this tool over alternatives.

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