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

With no annotations provided, the description carries full disclosure burden. It usefully reveals the pricing/auth model (GET via x402 at $0.04), the endpoint, and that output mirrors /v1/movers including volume surge ratios. It omits rate limits, pagination, and what the surge ratio actually represents, so the mutation-free read profile and return behavior are only partially covered.

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-loaded with the core value proposition, three tight sentences plus a bracketed endpoint/price/docs line that carries real operational info. Slight marketing filler ('The fastest way to see where news is landing') but no significant bloat.

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?

No output schema exists, and the description only gestures at the return shape by analogy to '/v1/movers', which the agent cannot see. Combined with 25% parameter coverage and no annotations, gaps remain around the category filter, result shape, and pagination.

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% (just min_liquidity documented), so the description must compensate. It echoes the window enum (1h/6h/24h) and references ranking/volume, but says nothing about limit's cap of 50, nothing about the category parameter, and oddly the enum includes non-climate values despite the 'pre-filtered to climate and weather' claim.

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 climate and weather probability moves' ranked by 'absolute probability change over your chosen window'. The clause 'pre-filtered to climate and weather markets' implies the distinction from the generic probability_movers and the many sibling category variants, but does not name them explicitly.

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?

'The fastest way to see where news is landing in climate and weather' gives implied usage context, but there is no explicit when-to-use/when-not, no prerequisites, and no named alternative (e.g. probability_board_climate, probability_movers for other categories). Guidance is inferred rather than stated.

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