find_similar_products

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

With no annotations, the description bears full burden. It discloses the algorithm (Jaccard similarity), but does not mention authentication, rate limits, error behavior, or what happens if the product is not found. Some transparency is provided but insufficient.

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?

Single sentence that is direct and contains no redundant information. Front-loaded with action and resource.

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 an output schema exists, return value explanation is not needed. However, the description lacks input format details and usage context relative to sibling tools. It minimally covers the tool's purpose but leaves gaps in practical use.

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 0%, so description must clarify the parameter. It only states the parameter name product_name without explaining format, valid values, or how to specify the product. The algorithm hint helps infer purpose but adds little semantic detail.

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?

Clearly states the tool finds skincare products with similar ingredients using Jaccard similarity, specifying both the resource (skincare products) and method (Jaccard similarity). It distinguishes itself from siblings like search_live_products which likely do not use ingredient similarity.

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?

No explicit guidance on when to use this tool instead of siblings like search_live_products or check_red_flags. The description implies use for ingredient-based similarity but lacks exclusions or prerequisites.

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