TradingView-only: crypto gainers/losers

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the return envelope label ('TRADINGVIEW') and enumerates accepted argument values, which helps, but it says nothing about rate limits, whether limit is capped, pagination, or error behavior on an invalid exchange.

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?

It is front-loaded with a one-line purpose followed by a compact Args/Returns block, and every line maps to a real parameter or the response. No filler sentences or restated title material.

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 four-parameter read-only lookup, the description covers all arguments and the response envelope, which is enough to call it correctly; an output schema also exists so return detail is not required. It omits defaults and any limit ceiling, but nothing essential to invoking the tool is missing.

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% and no enums are declared, so the description is the only source of valid values — and it delivers them for movement, exchange, and timeframe, plus a plain meaning for limit. The exchange list is left open-ended ('…') and no bound on limit is given, keeping it short of a 5.

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 first line states a specific verb and resource ('Top crypto gainers or losers on an exchange') and adds the qualifier 'TradingView-only', which separates it from the futures-oriented sibling futures_top_movers. It does not name that sibling explicitly, so differentiation is implied rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance relative to siblings such as futures_top_movers or crypto_volume_breakout. The 'TradingView-only' tag implies this is the TradingView data path for crypto movers, but the agent must infer the rest from the tool name.

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