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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, yet the description still adds real context: it is free, it is a state read not advice, and it honestly discloses that the studied trade was REFUTED at Robinhood retail fees. It omits return format and pagination, but the disclosure of the refutation is genuinely useful behavioral information.

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 front-loaded with the resource and scope, and each sentence carries information (what it returns, the study validation, the honest refutation caveat, and the free/not-advice tags). It is dense and somewhat promotional in tone, but there is little outright 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?

With no output schema and no parameters, the description carries the burden of explaining what comes back, and it does so reasonably well (the ranked coin, BTC 200-day gate, phase, study receipts). It stops short of describing the shape of the returned payload, but for a parameterless read tool it is fairly complete.

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 zero parameters, so there is no parameter semantics to document; the baseline for a no-parameter tool is 4. Nothing in the description misrepresents the (empty) input contract.

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 states a clear resource and scope: the top session-momentum coin heading into the 20:00 UTC signal, plus BTC regime gate, phase, and study receipts. It is highly specific about what is returned, but it never names or differentiates from the obvious sibling get_crypto_night_live, leaving the preview-vs-live distinction to inference.

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, and no routing to alternatives such as get_crypto_night_live. The reader can infer that a 'PREVIEW' is the non-live counterpart, but the description never states the condition that selects this tool over its sibling.

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