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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds return type details (best price, 30-day stats, offer link) but does not significantly extend beyond annotations. No behavioral contradictions.

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 bilingual and contains no filler, but the repeated content in German and English might be slightly redundant. However, it is front-loaded with the key action and resource.

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 simple two-parameter input, annotations covering safety, and output schema likely detailing return fields, the description provides sufficient context about what the tool does and returns. It mentions the key outputs (price, stats, link).

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 coverage is 100% and describes both parameters. The description adds critical usage constraint that exactly one of id/url must be provided, and gives an example URL format, which adds meaning beyond 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 it looks up a specific product by ID or URL, and returns best price, 30-day statistics, and offer link. It specifies the catalog (wogrill.de) and distinguishes from sibling 'search_offers' by focusing on a single product lookup.

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 explicitly requires exactly one of id or url, and explains the valid formats (ASIN, externalId, Amazon URL). It implies this tool is for targeted product lookup rather than broad search, but does not explicitly contrast with 'search_offers'.

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