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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the data is supplementary, not a primary signal, and is only meaningful for crypto assets. It does not discuss freshness, caching, or data sourcing, keeping it short of a 5.

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?

Content is front-loaded in a single dense sentence with two short supporting sentences. The parenthetical glosses on funding rate and SSR add interpretive value, though the metric list is packed tightly enough that a reader must parse it carefully.

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 zero parameters, an output schema present, and rich annotations, the description's remaining job is to state scope and what is returned, which it does fully. An agent has everything needed to decide whether to call it and how to weight the result.

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 no parameter semantics to describe and the baseline of 4 applies. The description does not attempt to document any inputs, which is correct here.

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 specific resource (crypto market context) and enumerates exactly what it returns: BTC/ETH dominance, total/alt market cap, Fear & Greed, perp funding rate and open interest, and Stablecoin Supply Ratio. It also scopes itself to crypto assets, which implicitly separates it from siblings like get_macro_context and get_sentiment_data.

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 explicit when-to-use guidance ('Use ONLY when analysing crypto assets (BTC, ETH, crypto ETFs)') and a clear caveat that it is background context rather than a primary signal. It does not name the alternative tools (e.g. get_macro_context, get_sentiment_data) an agent should prefer for non-crypto or sentiment-first analysis, so routing is only partly resolved.

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