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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that the price is a USD spot quote and specifies the accepted address formats per chain (EVM contract vs Sui coin type), but says nothing about behavior on unknown symbols, missing params, or stale/unavailable pricing.

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?

Front-loaded with the core purpose, and the chain-id enumeration earns its place because it maps to an opaque numeric enum. The single long sentence with nested parentheticals is dense but not padded.

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?

An output schema exists, so return values need no explanation; given that, the description covers both lookup modes, the currency, and the two address syntaxes across chain families. The only residual gap is the simultaneous symbol+address case, which is minor for a read-only price lookup.

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 only 33% (symbol and address are undescribed in the schema), and the description compensates well: it gives symbol examples (ETH, SUI) and explains that address means an EVM contract address or a Sui coin type like 0x2::sui::SUI. It does not clarify the interaction rule when both symbol and address are passed.

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+scope: 'USD spot price for a token'. The word 'spot' implicitly separates it from the historical sibling get_token_history_price, but neither that tool nor any other sibling is named, so the differentiation is left for the agent to infer.

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?

Usage is implied by the two lookup modes (symbol, or address+chain), but there is no explicit 'use this when', no exclusion of get_token_history_price, and no statement about what to do if neither symbol nor address is supplied despite zero required parameters.

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