compareProducts

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

With no annotations, the description must convey behavior. The phrase 'using AI' is vague and does not disclose specifics such as what data is returned, whether the tool is read-only, or any side effects. The agent cannot anticipate the comparison criteria or output format.

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 extremely short (one phrase), which makes it concise but lacking structure. It is front-loaded but omits necessary details, making it minimally adequate.

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 the two-parameter schema and no output schema, the description is incomplete. It fails to explain what the comparison yields, how results are presented, or any behavioral context. The agent would need to infer or test to understand the tool fully.

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%, so the description should clarify parameters. The parameter names 'nameOrBarcode1' and 'nameOrBarcode2' are somewhat self-explanatory, but the description adds no additional meaning or constraints (e.g., format, examples). The agent benefits only from the names, not the description.

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 action ('Compare') and the resource ('two products'), and mentions 'using AI' to indicate automated analysis. It distinguishes from sibling 'analyzeProduct' which is for single products. However, it lacks specifics on what aspects are compared, slightly reducing clarity.

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 provides no guidance on when to use this tool versus alternatives like 'analyzeProduct' or 'searchProducts'. No context on prerequisites or exclusions is given, leaving the agent uncertain about appropriate usage.

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