Top 24h crypto movers (universe scan)

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

The description adds meaningful behavioral context beyond the annotations: data refreshes on a ~60s tick, the scan is free and public, no API key is required, and symbols can collide so coinId must be passed instead. These details help the agent understand external constraints and side effects even though annotations already mark the tool as read-only.

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 description is compact but information-dense. Each sentence earns its place: definition and sort order, usage workflow with alternative tools, and critical data passing caveat plus refresh timing. It is front-loaded and there is no filler.

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?

The description, combined with the input schema, output schema, and annotations, provides a complete operational picture. It explains the purpose, workflow, return fields, refresh behavior, auth requirements, and intra-tool handoff guidance, leaving no major gaps for the agent.

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?

The input schema covers 100% of the two parameters with clear descriptions, so the baseline is 3. The description does not add extra meaning to limit or direction, but it does reinforce the top-movers framing which lightly aligns with direction.

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 clearly states the tool scans the full crypto universe for the biggest 24h price moves, specifically top gainers or losers ordered by 24h change percent. It uses a specific verb and resource and distinguishes itself from narrower tools like get_candles and get_market_context.

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?

Explicitly says to use this for discovering candidates beyond the watchlist, then deep-analyze each candidate with get_candles and get_market_context before trading. It also notes the coinId-passing convention and warns against re-resolving symbols, which gives clear operational guidance.

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