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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false, destructiveHint=false). The description adds real behavioral context beyond those: it enumerates what the output contains (curve lean, tighter/wider than Kalshi, crossing point, Kalshi's ladder centre, widest published gap, every listed strike) and discloses a coverage limitation (published number only at 30–70%). No auth or cost notes, so not a 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?

Front-loads the purpose, which is good, but the middle sentence is a long dash-chained run that piles multiple output elements together and is hard to parse on a single read. It is information-dense rather than wasteful, but it is not tightly structured.

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 carries the return-value burden and does so thoroughly, and annotations handle safety. It also handles the all-optional parameter surface by explaining the defaults. Slightly short of 5 only because the family/stat/player interaction and multi-market fallbacks could be spelled out more explicitly.

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 100%, so the schema already documents stat, team, family, and player, including the family default (spread first) and the season_wins pairing. The description restates the market types (spread / season win total / player prop) but adds no syntax, format, or edge-case detail beyond the schema, so the baseline 3 applies.

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?

Names a specific verb (explain) and a specific resource/scope (one NFL strike ladder: a game spread, a season win total, or a player prop), and enumerates the read categories it produces (SHAPE, LOCATION, PRICED, MARKET READ, QB HOLD). It does not explicitly contrast itself with close siblings such as explain_prop, explain_player, or nfl_ladder, so the boundary is left to inference.

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?

Provides concrete trigger phrasings ("explain the Chiefs win total ladder", "why does the ladder lean Browns", "what does SHAPE mean on <player> receptions") and a clear constraint that it is one ladder per call. No explicit when-not or alternative-tool routing is given, so it stops short of a 5.

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