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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the data is 'stored' observations 'with provenance', signaling historically captured snapshots rather than live lines, and that coverage may be incomplete. It omits pagination behavior despite limit/offset parameters.

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?

Two short sentences with the substantive point (stored observations with provenance) front-loaded. The second sentence is short but squandered on an unresolvable '/status' reference rather than useful routing.

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?

For a five-parameter query tool with no output schema and zero parameter documentation, the description is far too thin. An agent knows roughly what the data is but not how to scope a query, what paging does, or when to prefer an alternative odds/event tool.

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% across five parameters, so the description must carry the burden and does not. It mentions moneyline/spread/total, which loosely maps to the 'market' parameter, but says nothing about sport, event_id scoping, or limit/offset paging semantics.

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 names the resource ('moneyline, spread and total observations') and implies retrieval of stored odds, but never states a verb like list or fetch, and does not distinguish this from siblings such as get_sportsbook_events or get_sportsbook_history. The '/status' pointer references something outside the sibling tool set, adding ambiguity rather than clarity.

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?

'Check /status for current market coverage' is the only usage cue, and it points to a path that does not correspond to any listed sibling (get_coverage is the closest match). There is no guidance on when to use this versus get_sportsbook_events (upcoming events) or get_sportsbook_history, which an agent cannot resolve on its own.

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