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

Annotations already establish readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond them: the data refresh cadence ('refreshes every 30 minutes'), and a fairly detailed account of what each market mode returns (best book and price per side, cents spread, model chance and edge).

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 content is dense but front-loaded — books and purpose first, then each market mode, then refresh cadence. The middle sentence is long and run-on, but every clause carries information an agent needs; little is padding.

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 no output schema, the description correctly carries the burden of describing return contents for both market modes, and it does so concretely. It is nearly complete for a read-only comparison tool; the only omission is any mention of plan/row-limit interaction, which is left to the schema.

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 baseline is 3, and the description earns above baseline by explaining how parameters interact rather than repeating them: it ties 'player' to the hr market, states that 'market' selects the whole output shape, and echoes the default sorting behavior per market.

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 states a specific verb+resource: cross-book line shopping for moneylines, spreads and totals, plus a distinct HR-prop mode, and names the four books covered. It is clear what the tool does, but it never explicitly distinguishes itself from close siblings like invoke_mlb_game_odds, invoke_mlb_hr_board or invoke_nhl_odds_props, which an agent could plausibly pick instead.

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?

It gives clear operating context: 'market games (default)' for game lines, 'market hr (MLB only)' for home run props, and 'sport mlb, nfl or nhl'. That establishes an exclusion (hr is MLB-only) and a default mode, though it stops short of naming when to prefer this over the sport-specific odds tools.

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