crypto_market_overview

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

No annotations provided, so description carries full burden. It discloses what data is returned (market cap, dominance, active coins) but omits operational details like data freshness, caching behavior, or rate limits that would help an agent understand reliability and constraints.

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?

Single sentence with front-loaded verb and parenthetical elaboration. Zero waste: every word serves to identify the action, scope, and return specifics. Appropriate length for a parameterless tool.

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?

For a zero-parameter tool without output schema, the parenthetical list of returned metrics provides essential completeness. Would benefit from mentioning data source or freshness, but adequately covers the tool's function given its simplicity.

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?

Input schema has zero parameters (empty object) with 100% coverage trivially satisfied. With no parameters to document, the baseline score of 4 applies. The description appropriately focuses on return values rather than inventing parameter documentation.

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 uses specific verb 'Get' with clear resource 'global crypto market overview' and distinguishes from price-specific siblings (crypto_price, crypto_price_history) by listing aggregate metrics (total market cap, BTC dominance, active coins) that clearly signal this is for broad market analysis, not individual coins.

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?

Provides implied usage guidance through the specific aggregate metrics listed (suggesting use when needing market-wide stats), but lacks explicit when-to-use statements or comparisons to siblings like crypto_price or crypto_trending for specific coin data.

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