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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it is the cheapest price-check option and covers whole-market public data rather than user holdings. It does not describe freshness, rate limits, or response shape, but those gaps are minor given the annotations and output schema.

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 the core behavior and then uses short, purposeful sentences for cost guidance, alternative routing, and wallet-data clarification. No sentence is redundant or wasted.

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?

For a simple price lookup with an output schema and read-only annotations, the description is complete enough: it covers what the tool returns, when to prefer it, and which sibling to use for richer market data. The remaining parameter-format gap is small relative to the structured schema and output schema.

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 0%, so the description needs to compensate for parameter meaning. It only implies that 'one token' must be identified and never mentions `token_address`, its expected format, or the fixed `network` value, leaving the required parameter under-explained.

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 states a specific verb and resource: the current USD price of one token, and explicitly limits scope with 'and nothing else.' It also distinguishes this tool from `get_token_overview` and from the `get_my_` family, so an agent can select it without opening another schema.

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?

It explicitly says when to use it ('Cheapest call for a price check') and names the alternative plus the condition for choosing it ('use `get_token_overview` if you also need market cap, liquidity or volume'). It further clarifies when not to use it by stating that public market data is not the user's wallet data.

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