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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description adds the enumerated payload contents, but says nothing about data freshness, caching, or whether figures are real-time or delayed – relevant for a live market-data tool.

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?

A single efficient sentence with the headline metric (total market cap) front-loaded and no filler. It is a noun-phrase fragment rather than a framed statement, which slightly weakens the structure but wastes nothing.

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?

No output schema exists, so the description must convey return contents, and it lists the key metrics an agent needs to decide relevance. Units, value formats, and time-zone/freshness of the 24h change remain unspecified, a minor gap for a zero-parameter tool.

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 per the baseline this scores 4. There is nothing for the description to disambiguate beyond confirming the tool is unfiltered and global in scope.

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 exactly which metrics are returned (total market cap, 24h volume, BTC/ETH dominance, 24h change), so an agent knows what data this yields. It lacks a verb and does not differentiate itself from the sibling market_overview, which appears to overlap in scope.

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 statement of when to use this tool versus market_overview or get_price, and no exclusions or prerequisites. The agent must infer usage purely from the metric list.

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