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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely useful behavior the annotations cannot convey — the exact price ($0.002 USDC per successful call), the x402 payment rails (Base, Solana, Arc), and that failed calls are not charged. It also discloses the market taxonomy and that prices are American odds with 'even' mapped to +100, though it says nothing about freshness/latency of the scraped lines.

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 and data shape are front-loaded, and pricing is correctly placed at the end. The sibling sentences are repetitive in construction ('when you need ... odds screens: every listed') and the first sentence is a long comma-spliced run, but no sentence is purely filler.

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?

Given an output schema exists, the description needn't explain return values and doesn't, while still covering source, leagues, markets, pricing and alternatives. The main residual gap for a paid odds-scraping tool is timing/freshness of the lines and whether all eight books are always present.

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 coverage is 100%, so the schema already documents team, limit, league and market; the description only restates the market set (spread, total, moneyline) and league list. It adds modest meaning via the 'even is +100' price convention, but says nothing about limit behavior, defaults, or how team abbreviations are matched (schema covers the example 'NE').

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 ('Betting lines from VegasInsider's odds screens') and enumerates the leagues and returned fields (VI event ID, start time, rotation numbers, open/current lines per book, consensus). It explicitly separates itself from the sibling odds sources dev_covers and dev_fanduel, so an agent can route without opening any 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?

Names the two closest alternatives and the condition that selects them (dev_covers for Covers.com screens, dev_fanduel for FanDuel game lines only), which effectively implies this tool is the multi-book comparison source. It does not state explicit exclusions such as live/in-play betting or non-listed games, so it stops short of full when/when-not guidance.

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