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

With no annotations, the description carries the full burden. It usefully discloses the $0.01 USDC per-call cost via x402 and the 'live' nature of the data. It does not mention response shape, error behavior, rate limits, or whether the operation is strictly read-only, though 'market' implies non-mutating.

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?

One dense sentence with no filler. The market context, lookup mode, returned metrics, and cost are all front-loaded and each clause earns its place.

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?

The description covers purpose, input approach, key output metrics, and cost, which is solid for a simple lookup tool. However, there is no output schema, no explicit statement that slug or contract is required, and no guidance on what happens when both or neither are provided.

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%, so the schema already documents slug, chain, and contract. The description adds the clarifying idea that lookup is 'by slug/contract' and names the returned metrics, but it does not explain precedence or whether slug and contract are mutually exclusive alternatives.

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 identifies the resource: live market data for a CC0 asset, with specific token/NFT metrics. It differentiates from siblings like cc0pedia-search and cc0pedia-verify by focusing on market pricing and liquidity, though it lacks a direct action verb like 'get' or 'fetch'.

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 intended use is implied: call this when you need live price/FDV/liquidity/volume data for a CC0 asset. However, it does not explicitly state when to prefer this over cc0pedia or cc0pedia-search, and there are no exclusions or alternative routing instructions.

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