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

Annotations already declare this a safe, idempotent read. The description adds value by disclosing the payload contents (an image plus page, dates and banner metadata), which the agent could not infer otherwise since there is no output schema. It does not mention behavior when no crop exists or the size/format of the image.

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?

Two short sentences, contents first and usage second, with no filler wording. Every clause carries information.

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 one-parameter read tool with annotations covering safety and no output schema, the description adequately conveys what comes back and why to call it. The main omission is failure behavior when evidence is missing for a given offer.

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% and the single offerId parameter is undocumented in the schema. The description only implies the id refers to an offer; it does not say where to obtain a valid offerId, whether it must come from search_offers, or what happens with an unknown id.

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 states a specific resource: the flyer crop image an offer was read from, along with page, dates and banner. It is clearly distinct from siblings like search_offers (which finds offers) or price_history (which returns prices), though it never names those siblings explicitly.

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?

It gives two concrete use cases: showing the user the source evidence, and a price match at the till. That tells the agent when the retrieval is worthwhile, but it does not say when this is unnecessary (e.g. when a link or price alone suffices) or point to any alternative tool.

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