compareProducts

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

Lacks annotations; 'using AI' is vague. No disclosure of return format, performance, or side effects. Provides minimal insight into how the comparison works.

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 short sentence is concise but lacks essential details. It is not verbose, but underspecification reduces efficiency.

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 two parameters, no output schema, and no annotations, the description is too sparse. It does not explain what the comparison returns or how results are structured, making it incomplete.

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?

Parameters 'nameOrBarcode1' and 'nameOrBarcode2' are named suggestively but no description explains accepted formats (e.g., product name, barcode number, or both). Schema coverage is 0%, requiring compensation from description which is absent.

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 verb 'compare' and resource 'two products' using AI. It distinguishes from sibling tools like analyzeProduct which is single-product analysis.

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 guidance on when to use compareProducts versus sibling tools like analyzeProduct, searchProducts, or getProductByBarcode. No when-not or alternatives provided.

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