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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: the exact return shape and the enumeration of assessment labels (HIGH_RISK / ALT_RISK / ALT_FAVORABLE / OPPORTUNITY_WITH_CAUTION / NEUTRAL), which tells the agent what interpretation it will get back. No data-freshness or latency caveats are given.

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-loaded with the core purpose in the first sentence, then usage, then a structured returns list. Slightly verbose in the mid-paragraph ('Calling this once gives Claude the macro context to provide Bitcoin-aware commentary...'), which restates the already-clear value proposition, but nothing is truly 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?

With no parameters and no output schema, the description carries the full burden, and it does so: it names each returned field group (bitcoin, dominance, total_market, assessment) and describes the assessment reasoning. An agent can call this correctly and interpret the result without any further documentation.

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. The description correctly implies no inputs are needed ('Single-call... in one shot').

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+resource ('Single-call BTC macro context: price, dominance, total market cap + risk assessment') and enumerates exactly what it aggregates. It is clearly distinguishable from siblings like yahoo_price or coin_analysis, which cover single symbols rather than the aggregate market frame.

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?

Gives explicit trigger guidance ('Use this WHENEVER analyzing any cryptocurrency...'), including the altcoin case, and names the alternative workflow it replaces ('without chaining 2-3 separate yahoo_price + manual reasoning calls'). It stops short of stating when NOT to use it or where a sibling (e.g. coin_analysis) is preferred instead.

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