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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuinely useful context beyond them: metered/account-dependent access, an explicit empty-result caveat ('never infer coverage from an empty result'), a bounded single-request/no-retry/no-polling contract, and affiliate 27 exclusion. It stops short of describing result freshness or rate limits.

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 opening verbatim-restates the title ('List Hedge Opportunities (v2)'), wasting the most prominent position. The remainder is a choppy series of clauses whose value varies; some (affiliate 27, empty-result caveat) earn their place while others are terse fragments.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What remains missing is sibling differentiation and any explanation of the ten nested query parameters, leaving the agent under-informed for a moderately complex filtered-list call.

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 reported at 0% for a nested query object carrying ten properties (sort, type, limit, offset, event_id, market_id, min_percent, include_live, affiliate_ids, include_closed). The description only touches affiliate exclusion and says nothing about filter semantics, sort direction, pagination, or opportunity-type values, so it fails to compensate for the coverage gap.

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 gives a specific verb+resource ('List Hedge Opportunities') and clarifies the domain ('current arbitrage/hedge opportunities across sportsbooks'), so the agent knows what it returns. However, it never distinguishes itself from close siblings like v2GetHedgeOpportunitiesByEvent, v2GetHedgeOpportunityByID, or v2GetTopHedgeOpportunities, which an agent could easily confuse for the same capability.

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?

'Use returned canonical IDs' implies a chaining workflow, but the description never states when to prefer this tool over the event-scoped, ID-scoped, or 'top' hedge siblings. There is no when-to-use or when-not-to-use guidance, only operational constraints.

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