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

With no annotations present, the description carries the full burden — and it discloses a lot: exact pricing ($0.05 USDC per call via x402, pay-per-call), recompute cadence (~5 min, 24/7), and an honest methodology caveat that shapes were backtest-confirmed on equities but are only forward-graded on crypto. Telling the agent the read is paid and not crypto-backtested is precisely the behavioral context annotations would otherwise need to supply.

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?

Four sentences, each earning its place: the scan/output spec, the freshness cadence, the backtest methodology caveat, and pricing plus the free preview alternative. The core action is front-loaded in sentence one, 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?

For a zero-parameter, paid scanner with no output schema, the description covers the central decisions: what gets scanned, what a hit contains, freshness, cost, and how to preview via the free twin. The remaining gap is that domain terms like GO, fuel multiple, grade, and room are listed without definitions, and no output schema exists to fill that in.

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 is empty (zero parameters), so there is nothing for the description to add about arguments — the 0-param baseline of 4 applies. It instead previews the read's contents (GO, fuel multiple vs BTC, grade, room, setup column), which is output-side context rather than parameter semantics.

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 names a concrete verb and resource — scan all 81 Robinhood-tradable coins — and specifies the exact setup shapes sought (daily uptrend + washed-out 5-minute tape). It distinguishes itself from sibling get_crypto_setups by calling itself the paid full-universe read versus the free hit-count/top-3 preview.

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?

It explicitly names the free twin get_crypto_setups as a preview option 'so you can judge it before buying', giving the agent a concrete route to the cheaper alternative. It does not cover when to prefer other live crypto probes like get_crypto_day_live, but the free-twin routing addresses the main decision an agent faces for this paid tool.

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