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

Annotations already establish read-only, idempotent, open-world, non-destructive. The description adds genuinely useful operational traits beyond them: access/delay/metered usage tied to the connected account, a single bounded request with no polling or retry, and no wagers/account changes. It doesn't state rate limits or pagination, so a 4 rather than 5.

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?

It is front-loaded with purpose and dense rather than bloated, but the sentences are fragmented and run-on ('Read-only Product data or price calculation'), mixing unrelated caveats. Some clauses (no wagers/guarantee of returns) feel like boilerplate that dilute the core delta semantics.

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 needn't be explained, and the description does cover several constraints. But for a delta/cursor tool the semantic core (what last_id means, what a delta represents) is missing, leaving the definition adequate but with a real gap an agent would need.

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%, so the description must carry the parameter burden, and it largely doesn't. The required query.last_id — the core cursor parameter for a delta endpoint — is never explained, and sport_id is untouched. Only the affiliate exclusion note tangentially relates to affiliate_ids, which already has its own inline 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 opening phrase 'Get event deltas (V2 format via V1 path)' essentially restates the name and title, though the 'V2 format via V1 path' clause does hint at a compatibility shim. It names the resource (event deltas) but never says what a 'delta' actually is here (changed events since last_id?), and with v1GetDelta, v2GetDelta, and v2GetMarketsDelta as siblings, the agent cannot confidently distinguish them.

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?

There is partial guidance ('Use returned canonical IDs', 'never infer coverage from an empty result'), but no when-to-use or when-not-to-use versus the sibling delta tools. 'Affiliate 27 is excluded' is a scope note, not usage direction. The agent is left to infer the alternative.

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