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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the bar is lower; the description still adds that the call is free and that returned prices are non-binding, which is exactly the kind of caveat an agent needs before acting. Pagination and rate-limit behavior are left to the schema.

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 short sentences, front-loaded with the resource and categories, then the cost and pricing caveat. No filler or repetition.

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?

With no output schema, the description is nearly complete for a filtered-list tool: what it returns (offers by category/country), cost, and price caveat are covered, and pagination lives in the schema. It could say slightly more about the shape of returned offer objects (the `brand` field is only referenced in the schema).

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 documents every parameter including pagination semantics and ISO-3166 format. The description only restates the country scoping and the category meanings already embedded in the `type` enum, so baseline 3 applies.

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?

States a specific verb (browse) and resource (purchasable offers) and enumerates the four offer categories, which map directly onto the `type` enum. An agent can immediately distinguish this from buy/quote/fx siblings, which transact rather than list.

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?

'Free' plus 'prices shown are indicative; the quote fixes them' tells the agent this is a zero-cost discovery call and that a follow-up `quote` is required for a binding price — that is real routing guidance. It stops short of naming the sibling tool explicitly or stating when not to use it.

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