compare_products

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

With no annotations, the description must carry the behavioral burden. It discloses that calls run in parallel, that the tool accepts 2–5 items, and that results are live fields identical to get_product. It does not cover error handling or invalid inputs, but the core behavior is transparent enough for a fetching/comparison tool.

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 three short sentences, front-loaded with the core action and outcome. Every sentence adds value: input source, return shape, and when to prefer this tool. No filler or 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?

For a one-parameter tool with an output schema, the description is nearly complete: it defines the operation, input source, count limit, and return shape. It could additionally state what happens when fewer than 2 or more than 5 items are provided, but that is a minor gap and does not prevent correct invocation.

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 provides no description for pid_or_urls, so the description compensates by explaining it accepts pids or URLs sourced from search_products and expects 2–5 items. It does not specify URL formats or behavior for invalid entries, but this is solid semantic guidance for the single parameter.

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?

States a specific action ('Fetch 2–5 Flipkart products in parallel') with a clear outcome: side-by-side comparison. It distinguishes itself from get_product by emphasizing parallel fetching and comparison, and from search_products by being a comparison tool. The purpose is immediately obvious.

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?

Explicitly tells the agent where inputs should come from ('Pass pids or product URLs from search_products') and gives a clear use case: use this instead of mixing remembered prices with a new search. It does not explicitly say 'use get_product when you need a single product,' but that exclusion is strongly implied.

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