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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds the genuinely important behavioral fact that output is a trimmed preview (top-3 of 81 Robinhood-tradable coins) rather than the full universe, plus the constituent parts of the payload and the disclaimer that it is not advice. It omits any statement about refresh cadence, and its 'live ... not a delayed copy' claim sits awkwardly next to the get_crypto_day_live sibling, muddying rather than clarifying freshness semantics.

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 payload description is front-loaded reasonably well, but the opening rhetorical question ('Which crypto coins are in an uptrend right now?') is a hook rather than a purpose statement, and fragments like 'A state map, not a ranking or advice.' and 'Free.' are promotional padding on a ~90-word description for a zero-argument tool.

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-param, read-only tool with rich annotations and no output schema, the description covers what the response contains and that it is a limited slice, which is what an agent most needs. What it does not resolve is the routing question — how this differs from get_crypto_day_live and the other day/night board tools — which is the main open decision an agent faces here.

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 nothing for the description to disambiguate; baseline 4 applies.

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 payload — a top-3-of-81 crypto day-state preview with a BTC anchor, daily BTC/ETH gate regime and breadth counts — so the resource is identifiable. But it never uses a clear verb, and it does not distinguish itself from the many adjacent board tools (get_crypto_day_live, get_crypto_trend, get_full_board, get_day_board); in fact it claims to be 'a live trimmed slice ... not a delayed copy', which makes it harder to tell apart from its own _live sibling.

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. The phrase 'trimmed slice of the full state map' weakly implies the full map lives elsewhere, but no sibling is named and no alternative is offered for the agent that needs all 81 coins or a historical/delayed view.

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