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

No annotations are provided, so the description carries the transparency burden, and it does: it discloses the $0.005 USDC per-call cost, the ~5-minute publish interval, and the 'when the market moved' condition. It also specifies scope (all 81 coins) and output nature (state map not ranking). It does not mention rate limits or response format, but the key behaviors are covered.

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 core value proposition, then packs a dense list of included metrics, followed by update cadence, a clarification, an alternative, and pricing. Each clause adds information and nothing feels repetitive or wasted.

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 and many siblings, the description gives enough context to decide when to call it and what to expect: full coin list, metrics, freshness, pricing, and a fallback for users without a wallet. The enumerated fields compensate for the absence of an output schema.

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 has zero parameters, so the baseline is 4 and there is no parameter documentation burden on the description. The description implies a no-argument interface by describing the fixed scope of the returned board. No additional parameter semantics are needed.

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 identifies a specific resource: the full 24/7 crypto day-state board covering all 81 Robinhood-tradable coins, and enumerates the metrics included. It distinguishes itself from get_crypto_day by noting the full board versus a free top-3 preview. Though it lacks an explicit verb, the name and 'board' phrasing make the retrieval action clear.

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 gives an explicit routing rule: 'No wallet? get_crypto_day is a free live top-3 preview,' implying this tool requires a wallet or payment. It also clarifies that this is a state map, not a ranking, telling an agent when this tool fits. However, it does not contrast against the many other live crypto siblings like get_crypto_night_live or get_crypto_trend_live.

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