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

Annotations already establish readOnly/idempotent/non-destructive safety, but the description adds real behavioral value: a 48-hour freshness window, a warning that prices and stock can change after checking, and a required commission disclosure. These operational caveats are not derivable from the structured fields.

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?

Front-loads the core purpose and scoping in the first sentence, then moves to return fields, usage, caveats, and disclosure. Five sentences may seem long, but each carries distinct, non-redundant information, so little is wasted.

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 usefully enumerates the returned fields (Stymie URL, offer URL, price, savings, checked_at), which an agent needs. Missing detail on what the category/limit inputs control is the main gap, but the read-only nature keeps the bar low.

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 description never mentions either parameter. It says nothing about the 'limit' cap or the 'category' enum (ball/driver/putter/rangefinder/launch_monitor), so it fails to compensate for the coverage gap even though the raw schema values are fairly self-explanatory.

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 (get) plus a tightly-scoped resource (golf-equipment sale offers) with two precise qualifying conditions: in stock when checked within the last 48 hours and checked price below list price. This clearly separates it from generic siblings like search_equipment, which returns products rather than filtered deals.

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 makes the inclusion criteria explicit (48-hour freshness, price below list) and prescribes how to use results (link products to the Stymie URL, use the offer URL for merchants, disclose the commission). It stops short of naming or excluding an alternative such as search_equipment, so it is clear context without exclusions.

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