get_global_crypto_market

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes what data is returned but does not mention critical behavioral traits such as data sources, update frequency, rate limits, authentication needs, or error handling. For a data-fetching tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence that front-loads the purpose ('Get global crypto market overview') and lists key metrics without unnecessary words. Every element earns its place, making it highly concise and well-structured for quick understanding.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the purpose and output metrics but lacks behavioral context (e.g., data freshness, limitations). For a straightforward read-only tool, it meets minimum viability but could benefit from additional operational details.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose and output metrics, adding value by specifying what data is retrieved without redundant parameter details. Baseline is 4 for zero-parameter tools.

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 specific action ('Get') and resource ('global crypto market overview'), listing the exact metrics returned: total market cap, BTC dominance, 24h volume, and active coin count. It distinguishes this tool from siblings like get_crypto_price (single price) or get_top_movers (movement-focused) by emphasizing a comprehensive market overview.

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?

The description implies usage for obtaining a broad market snapshot, but does not explicitly state when to use this tool versus alternatives like get_fear_greed_index (sentiment) or get_portfolio_summary (personal holdings). It provides context but lacks explicit guidance on exclusions or comparisons to sibling tools.

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