compare_offers

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

The description discloses that the tool stores offers and returns a comparison overview, but lacks details on whether it updates existing entries, side effects, or authorization needs. Without annotations, more behavioral context is expected.

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 mostly concise with a logical structure: German summary, then English explanation, then parameter details. The redundant German sentence could be omitted for better conciseness.

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?

The description explains the tool's purpose and parameters adequately, but does not describe the output format of the comparison overview, which is a gap given no output schema. Additionally, constraints or error handling are absent.

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 0% description coverage, leaving the parameter structure unclear. The description compensates by listing expected fields (merchant_name, price, etc.) for each offer object, adding critical meaning beyond the schema.

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 compares offers for a purchase intent. The verb 'compare' and resource 'offers' are specific, and the context of a purchase intent distinguishes it from siblings like 'list_purchases' or 'create_purchase_intent'.

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 the tool is used after creating a purchase intent and collecting offers. However, it does not explicitly state when not to use it or mention alternative tools, leaving some ambiguity.

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