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

The annotations only flag readOnlyHint and openWorldHint, so the description has to explain how pricing actually happens, and it does: thin pools (under $2,000 in range or missing) fall back to a $10 buy routed through 0x with a warning, and Solana mints are priced from a small USDC buy across DEXes. That fallback behavior, including the real trade and the warning, is exactly the kind of context the annotations cannot convey.

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 core purpose is front-loaded in one clean sentence, and the chain-dependent pricing behavior follows in a single dense parenthetical. It is information-heavy but every clause earns its place, with only slight compression cost to readability.

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?

There is no output schema, so the description has to state the returns itself, and it does: price, market cap, and a fallback warning. For a 2-parameter read-only quote tool that is close to complete, with only minor gaps around output shape or units.

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?

With 100% schema coverage, the baseline is a 3, and the description earns more by explaining the dual meaning of `address` (0x contract vs Solana mint) and what the default chain does. It adds real meaning beyond the schema text, though the enum values themselves add nothing new.

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 opens with a specific verb-and-resource pair ('Price and market cap of any token by its contract address') and then pins down the address-type-to-chain mapping. That is enough for an agent to distinguish this from token_risk, eth_price, stock_quote or swap_quote without opening the 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 gives clear selection context: a 0x address defaults to Robinhood Chain, and you pass base, ethereum, arbitrum or solana to target those. It never says when *not* to use it, or when a sibling like token_risk or swap_quote is the better call, so it falls short of a 5.

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