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

No annotations are provided, so the description carries the disclosure burden. It does reveal the data source (CoinGecko) and the high-level payload, which is useful. However, it omits any behavioral context about the optional q parameter, data freshness, rate limits, or whether the result is real-time, leaving an adequate but not rich disclosure.

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 one compact, front-loaded sentence that conveys the core function and source without wasting words. It is somewhat telegraphic and lacks a verb, but it remains efficient and scannable.

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?

The description is sufficient for a basic no-argument call, and the presence of an output schema likely covers return shape. However, the unexplained q parameter and the lack of any sibling comparison leave the definition incomplete for correct invocation in ambiguous or filtered use cases.

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 schema exposes a single optional q string with default '', but the description never explains what q controls (e.g., currency, sorting, or query format). With 0% schema description coverage and zero explanation in the description, an agent cannot know valid values or whether to pass this parameter at all.

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 clearly identifies the resource ('Crypto Market') and the specific data returned (global market cap, BTC dominance, 24h volume) with the source (CoinGecko). It lacks an explicit verb and does not contrast with sibling tools like cryptoprice or coininfo, but the meaning is unmistakable.

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?

No guidance is given on when to use this tool versus the many sibling crypto tools such as cryptoprice, coininfo, or crypto. The description states what the tool returns but provides no trigger conditions, prerequisites, or exclusions.

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