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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds meaningful behavioral context: offers must be checked within 48 hours, be in stock, and have a price below list. It also transparently discloses that links may be affiliate links, providing additional insight beyond the schema and annotations.

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 three sentences long, front-loaded with the core purpose, and every sentence adds value: what the tool returns, the freshness/availability criteria, and the affiliate link disclosure. There is no redundancy or filler, making it highly efficient.

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 tool's simplicity, the description is fairly complete: it states what is returned and the key constraints. However, there is no output schema and the description does not describe the result shape (e.g., fields like price, link, or product name). Since the tool is straightforward and annotations cover safety, the missing return-shape details are a minor gap rather than a critical one.

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 schema has 2 parameters (limit, category) with 0% description coverage, so the description carries the burden of explaining them. The description mentions "golf equipment" but does not explain how limit controls the number of results or how category filters deals. The schema's enum for category offers some inherent meaning, but the description does not compensate for the lack of parameter-level documentation.

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 uses a specific verb-resource combination, "Get currently verified sale offers for golf equipment," clearly identifying the tool's function and domain. It distinguishes itself from sibling tools like search_equipment by emphasizing "verified sale offers" and the specific filtering criteria, making its unique purpose evident.

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 provides clear context for when this tool is appropriate by specifying that it returns only verified, in-stock sale offers below list price. It does not explicitly name alternatives or state when not to use it, but the criteria strongly imply use cases involving deal discovery rather than general equipment search.

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