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

Goes well beyond the annotations (readOnly/idempotent/openWorld) by disclosing metered usage tied to the connected account, a single bounded request with no background polling or automatic retry, affiliate 27 exclusion, and the absence of wagers or return guarantees. These are operational traits an agent cannot infer from structured fields 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 purpose is front-loaded, but the text lapses into terse fragments ('Read-only Product data or price calculation.') and an awkward clause about access/delay/metered usage. Several phrases are dense and under-explained rather than genuinely concise.

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?

Return values are covered by the output schema and the safety profile by annotations, and the description adds metering, retry policy, and exclusion caveats. It is largely complete, though it omits any parameter-level guidance for a tool with a nested, fully undocumented query object.

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%, yet the description explains none of the query parameters (sort, limit, offset, min_percent, include_live, include_closed, market_id). Only indirectly does it touch event_id ('canonical IDs') and affiliate_ids ('Affiliate 27 is excluded'), leaving most parameters unelaborated.

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+resource ('Returns arbitrage/hedge opportunities') scoped to 'a specific event', which cleanly separates it from the unfiltered v2GetHedgeOpportunities and the single-item v2GetHedgeOpportunityByID. An agent can identify the tool's function without opening the schema.

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?

Provides clear operating context: use returned canonical IDs, one bounded request with no polling/retry, and interpret empty results carefully. It never names a sibling alternative (e.g. v2GetTopHedgeOpportunities or v2GetHedgeOpportunityByID) or an explicit when-not condition, so it stops short of full routing guidance.

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