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

Adds real context beyond the annotations: metered usage and delay follow the account, empty results don't imply no coverage, affiliate 27 is excluded, and no retry/polling is expected. Annotations already cover the read-only/idempotent/non-destructive safety profile, and the description complements rather than repeats them.

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?

Purpose is front-loaded, but the body reads as template boilerplate with clipped fragments ('Read-only Product data or price calculation.'), which costs clarity. Sized acceptably but not tightly edited.

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 an output schema present, return values need not be described, and the annotations plus description together cover safety, usage limits, and the affiliate exclusion. The remaining gap is parameter-level detail for the query options.

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?

Top-level schema description coverage is 0% (path and query carry no description), so the description must carry the load, yet it only restates the affiliate-27 exclusion already present in the nested schema and says nothing about limit, offset, min_peers, or sample_limit semantics. It adds little parameter meaning.

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 (Get) and resource (Bookmaker Outliers) and defines the concept precisely: prices most out of line with peer-book consensus for matching event, market, period, participant, and line. It does not explicitly distinguish itself from the close sibling v2GetOutliers, so it stops short of a 5.

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?

Implies when to use it via the sport/date scoping and the 'one bounded request, no background polling or automatic retry' constraint, and warns against inferring coverage from an empty result. But it never names an alternative or states when to prefer this over v2GetOutliers or the steamers endpoints.

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