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

Annotations declare readOnlyHint=true and destructiveHint=false, which the description aligns with. The description adds that the tool returns matching products with prices, images, and checkout, and that it does not score or filter like skincare_recommend. This enriches transparency beyond annotations, though it could mention pagination or rate limits.

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 four sentences, well-structured with clear sections: purpose, usage guidelines, return behavior, and comparison. Every sentence earns its place; no redundancy. Front-loaded with the primary purpose.

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 4 parameters, no output schema, and the tool's search/browse nature, the description covers expected usage, edge cases (when not to use), and return behavior. The sibling list provides further context. No gaps identified.

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%, so baseline is 3. The description adds context for the category parameter ('Do not guess categories – only use if user explicitly mentions a catalog category'), which adds decision-making value beyond the schema. No major gaps, but does not elaborate on max_price or max_results beyond schema defaults.

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's purpose: 'Browse and search the product catalog.' It lists specific use cases (look up products, browse by category, compare options) and distinguishes from sibling tool skincare_recommend. The verb 'search' and resource 'product catalog' are explicit.

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?

Provides explicit when-to-use ('user wants to see what's available...') and when-not-to-use ('Do not use when user needs personalized recommendations – use skincare_recommend instead'). Also explains behavioral difference from the sibling tool, giving clear guidance on tool selection.

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