Compare Galaxus products

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

With no annotations, the description carries the full burden. It discloses the return shape ('Returns one detail object per input'), which is useful, but does not mention error handling for invalid inputs, behavior when some IDs fail, ordering, or rate limits. This is a notable gap for a batch operation.

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?

Two sentences, front-loaded with the action, no fluff. The first sentence states the purpose, the second clarifies the return format. Every word earns its place.

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?

For a simple one-parameter tool, the description explains the core function and return shape. However, without an output schema or annotations, it lacks details on partial failures, response ordering, or whether 'full details' matches get_product. The essentials are present, but edge-case behavior is unspecified.

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 schema already covers the parameter fully with '2-8 product ids, slugs, or URLs to compare.' The description repeats 'by id, slug, or URL' and 'several products,' adding no new semantic detail beyond what the schema provides. High schema coverage means baseline 3 is appropriate.

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 fetches full details for several products at once, with a specific verb ('Fetch') and resource ('products'), and includes the purpose 'for side-by-side comparison.' This distinguishes it from sibling tools like get_product (single product) and search_products (search), making its role unambiguous.

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 implies usage for batch fetching and comparing multiple products, but does not explicitly contrast with alternatives like get_product for single items or search_products for discovery. It provides clear context but lacks explicit exclusions or alternative tool guidance.

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