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

No annotations exist, so the description carries the burden. It discloses the ranking logic (absolute probability change, volume surge ratios) and that it is pre-filtered to NBA markets. However it does not mention rate limits, auth requirements beyond the x402 price note, or anything about error/pagination behavior.

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 core first sentence is front-loaded and tight. But the bracketed HTTP/price/docs metadata is shoehorned in and inflates the length without aiding tool selection or invocation behavior.

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 list tool with no output schema and no annotations, the description should say more about return shape, empty results, and the meaning of volume surge ratios. It is adequate to call the tool but leaves real gaps about behavior and the odd category parameter on an already-NBA-filtered endpoint.

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 only 25%, so the description must compensate. It explains the window semantics (1h/6h/24h) which is the key required param. But the optional category and min_liquidity params are not addressed at all, and given the tool is already NBA-filtered, the presence of a full category enum is semantically confusing and undocumented.

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+scope: 'Biggest NBA basketball probability moves (1h/6h/24h)', pre-filtered to NBA markets. This clearly distinguishes it from the generic probability_movers and from sibling sport variants like probability_movers_sports-nfl.

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?

Implied usage is clear ('The fastest way to see where news is landing in NBA basketball'), positioning it as a news-reaction tool versus the board/calendar siblings. But there are no explicit when-not-to-use statements, e.g., it never says to use probability_board_sports-nba when you want absolute levels rather than deltas.

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