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

Annotations only provide readOnlyHint true. The description goes beyond by explaining unknown symbol auto-resolution against 'the full CoinGecko coin list', the unsupported nature of 'Bare 0x contract addresses', and the batch cap. These are meaningful behavioral details not present in the annotation.

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?

Six sentences, each carrying specific information: purpose, accepted input forms, resolution behavior, batch limit, address limitation, and reuse guidance. No filler or redundant phrasing; the main purpose is front-loaded.

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 an output schema present, return-value documentation is unnecessary. The description covers input flexibility, resolution behavior, batch constraints, and a reuse recommendation, making it comprehensive for a token-price lookup tool. There are no obvious missing behavioral expectations.

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% with parameter descriptions already present, so the baseline is 3. The description adds value by revealing that full token names are accepted and that unknown symbols resolve automatically, which the schema does not mention. This enriches parameter understanding.

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?

Description states 'Get current price, 24h change, market cap, fully-diluted valuation, and volume for one or more crypto tokens' — a specific verb and resource, clearly distinguishing it from siblings like get_token_price_historical by emphasizing 'current'. The tool's scope is unambiguous.

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?

Explicitly instructs 'If get_wallet_portfolio already returned price_usd/value_usd for a held token, reuse that value instead of calling get_token_price again', providing a clear when-not-to-use alternative. It also spells out accepted identifier types (symbols, names, CoinGecko IDs) and the 50-token batch limit, offering concrete selection guidance.

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