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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add real behavior beyond them: it renders a visual card rather than prose, preserves the caller's ordering, names each row's nearest store, and explicitly adds no new offers. It says nothing about what happens with duplicate, stale, or out-of-coverage offer IDs, which is the main behavioral unknown for this tool.

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?

Three front-loaded sentences with no filler: purpose, inputs, and when-to-use. Slight compression cost in the phrase "titled Gaurmon card of flyer offers," which reads awkwardly on first pass, but nothing is redundant.

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 read-only render tool with no output schema, the description covers the essential contract: inputs come from prior searches, caller controls order, no new offers are introduced. It stops short of describing the rendered result's limits (e.g., behavior when an offer ID is invalid or outside the radius), which is the remaining gap.

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 100%, so the baseline is a 3, and the schema already states that offerIds is shown in order with a cap of 20. The description does add useful semantics beyond the schema: the ordering intent ("in your order") and the requirement to pass the same `near` so each row resolves to its nearest store.

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?

Specific verb and resource: "Show the user a titled Gaurmon card of flyer offers you chose, in your order." It immediately distinguishes itself from writing a list out and from the discovery tools (search_offers, compare_items), so an agent can place it among its siblings without opening the schema.

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?

Explicit when-to-use: "when the user asks to see, list or rank offers you've already found, instead of writing the list out," plus named upstream sources (search_offers, compare_items) and the constraint "Adds no new offers." The only gap is that it never states the negative case directly (e.g., there is nothing to show yet, go search first), leaving that to inference.

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