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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that data is 'live', implying real-time freshness, but says nothing about rate limits, auth, or data provenance beyond that. Adequate but not rich.

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?

Two sentences, front-loaded with the resource and its fields, followed by the invocation cue. No filler or redundancy.

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?

With a rich output schema and full annotations, the description need not explain returns; it covers scope and a usage trigger. It is largely complete, though missing sibling differentiation leaves slight ambiguity among the many market-data tools.

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?

Schema description coverage is 100%, with both ids and vs_currency documented including slug format and default. The description adds only 'for any coins', so baseline 3 is appropriate; it does not add meaning beyond the schema.

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?

States a specific verb+resource (get live crypto prices/market data) and enumerates the exact fields returned: spot price, market cap, 24h volume, 24h change, with example coins. Clear but does not differentiate itself from siblings like get_market_quotes or get_market_dominance.

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?

Gives an explicit trigger: 'Call for any price, market cap or volume question.' This is clear context for invocation, though it names no exclusions or alternative sibling tools for overlapping needs (e.g. dominance or market brief).

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