Get market context

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds important context: 'Facts only — no generated thesis' and 'Paper trading only — virtual funds (50,000 mUSD).' No contradictions 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 a single paragraph but effectively uses a list-like structure (price, change, market cap, etc.) to convey what is included. It is front-loaded with the core purpose, though slightly longer than necessary.

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 of the tool (multiple data types, output schema exists), the description covers all key elements: price data, category tags, sentiment, Fear & Greed, prediction markets with details, and similar coins. It also specifies limits ('up to 3', 'up to 6') and states 'facts only.' This provides complete context for the agent.

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%. The description adds meaning beyond the schema for coinId by clarifying it is a 'coin UCID' obtained from resolve_symbol. The agentTrace parameter is adequately described in the schema, and the description does not need to elaborate further.

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 provides 'compact factual context for ONE coin to form a thesis' and enumerates the included data: price changes, market cap, category tags, sentiment, Fear & Greed, prediction markets, and similar coins. This distinguishes it from siblings like get_candles or resolve_symbol.

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 explicitly instructs to 'call resolve_symbol first to get the coinId,' providing clear prerequisite guidance. It also notes 'paper trading only' and 'not financial advice.' However, it does not explicitly state when not to use this tool or mention alternative tools for other cases.

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