compare_products

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost none of it. It does not say whether the comparison is read-only, whether both ID arrays must be non-empty, how results are ordered, or what the response shape looks like. The list of included aspects ('identity, variants, specs and offers') is a hint about output content but not a behavioral trait.

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?

A single sentence with the verb and resource front-loaded and no filler. It is efficiently sized, though the trailing enumeration of comparison aspects is slightly compressed rather than informative.

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 tool with no annotations, no output schema, and 0% parameter coverage, the description is too thin. An agent knows it compares products but not how to source the required IDs, what constraints apply, or what the comparison result contains beyond a keyword list.

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 0% for both parameters, so the description must compensate and largely does not. 'Products' and 'across stores' loosely imply the product_ids and store_ids arrays, but there is no guidance on ID format, whether IDs must come from a prior search/list call, array size limits, or whether the two arrays are paired or crossed.

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 pairs a specific verb ('compare') with a specific resource ('products') and scopes it ('across stores'), then enumerates the axes of comparison (identity, variants, specs, offers). It is clear what the tool does, though it does not explicitly separate itself from siblings like compare_offers or compare_prices, whose names suggest overlapping territory.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives. With siblings such as compare_offers, compare_prices, and analyze_offers available, the agent is left to infer why it would pick this tool over those, which is exactly the ambiguity the description should resolve.

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