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

Annotations already establish read-only, idempotent, and non-destructive behavior, and the description adds substantial operational context beyond them: null delivery cost or total means unknown rather than zero, pagination must continue while has_more, and affiliate links carry a required disclosure. These are important behavioral traits that an agent would not get from the annotations alone.

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 front-loaded with purpose and then gives short, useful operational rules about output fields, null handling, pagination, and affiliate disclosure. Every sentence carries relevant information and there is no wasteful 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?

For a complex listing tool with an output schema and annotations, the description covers the highest-risk behaviors: unknown totals, incomplete pagination, and commission disclosure. Its main gap is that it does not sufficiently explain the many input parameters or alternative tools, but the schema and output schema reduce the overall burden.

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 tool has 14 parameters and only 50% schema description coverage. The description does not explain the required parameters' distinctions (variant_id, market_id, currency, destination_country) or optional filters such as condition, availability, merchant_id, sort, and limit, so it does not compensate for the incomplete schema semantics.

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 verb and resource: list offers, scoped to one exact variant and an explicit comparison context. This is clear enough for an agent to understand the operation, but it does not explicitly differentiate the tool from siblings such as compare_items, get_price_history, or search_products.

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 a clear usage context ('for one exact variant and explicit comparison context') and includes operational guidance about pagination and preserving unknown values. However, it does not explicitly say when to use this tool versus compare_items or get_price_history, nor does it name any exclusions.

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