Get market context

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

Beyond annotations (readOnlyHint, destructiveHint), the description adds detailed behavioral context: paper trading, virtual funds, execution cost disclosure, fee structures, and the fact that it returns facts only. No contradiction with annotations.

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 front-loaded with a clear summary of contents. It is well-structured, but the execution model details are somewhat lengthy and could be placed elsewhere. However, every sentence adds value.

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 complexity (multiple data components), the description covers the output comprehensively. It does not mention error handling or edge cases, but for a read-only tool with good annotations, this is sufficient.

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 coverage is 100%, so baseline is 3. The description adds meaning by explaining coinId format and how to obtain it ('Use resolve_symbol to find it'). The agentTrace parameter is already well described in 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?

The description explicitly states it provides 'compact factual context for ONE coin' and enumerates all returned data (price, changes, market cap, category tags, sentiment, Fear & Greed, prediction markets, similar coins). This clearly differentiates it from sibling tools like get_candles or get_portfolio.

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 instructs to 'Call resolve_symbol first to get the coinId' and notes 'Paper trading only'. It implies usage for factual context gathering without analysis. While it does not explicitly state when not to use it, the context is clear and the prerequisite is provided.

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