cmc_global_metrics

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

No annotations are provided, and the description does not disclose any behavioral traits such as data freshness, rate limits, authentication requirements, or any side effects. The word 'Get' implies a read operation, but more detail is needed.

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 extremely short (one sentence), but it lacks necessary detail to be useful. Conciseness is not helpful when essential information is omitted.

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?

Given the simplicity (one parameter, no output schema), the description should provide context on expected return values or data structure. It fails to do so, leaving the agent uninformed about what 'market metrics' means.

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 only parameter (api_key) has no description in the schema (0% coverage), and the tool description does not explain its purpose or requirements. The description adds no value beyond the schema structure.

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 states the tool gets 'global cryptocurrency market metrics' from CoinMarketCap, distinguishing it from sibling tools like cmc_listings (individual coin listings) or cmc_quotes (specific coin quotes). However, it does not specify what specific metrics are included (e.g., total market cap, volume).

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 on when to use this tool versus alternatives (e.g., cmc_listings, cmc_trending). No mention of prerequisites or conditions. The description implies using it for global metrics, but lacks explicit usage context.

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