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

Goes well beyond the readOnly/openWorld annotations by disclosing refresh cadence (~every 5 minutes, 24/7), the auth/subscription requirement, the x402 pay-per-call path, and the explicit failure mode (PaymentRequired with no data). It also discloses the backtest/forward-grade provenance of the setup shapes.

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-loads the scan scope and return contents, then cadence and payment terms. Mostly efficient, but there is mild redundancy ('Live intraday version' restates the already-implied live framing) and heavy capitalized emphasis that adds bulk without adding information.

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 tool with no output schema, the description supplies the return fields (GO, fuel multiple vs BTC, grade, room, setup column), the refresh cadence, and the payment gating failure mode. Nothing an agent needs to invoke it correctly 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?

The tool takes no parameters, so there is nothing for the description to add; the baseline for a zero-parameter tool applies. No parameter meaning is missing because none exist.

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 and resource — scanning all 81 Robinhood-tradable coins for defined washed-setup shapes — and explicitly frames itself as the 'Live intraday version,' distinguishing it from the non-live get_crypto_setups sibling. An agent knows exactly what this returns without opening the schema.

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?

Prerequisites and context are clear: it is the live/intraday read, requires a Coil Live subscription (or x402 pay-per-call), and otherwise returns a PaymentRequired object. However, it never names the alternative (get_crypto_setups) or states when to prefer cached vs live, leaving the sibling choice implicit.

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