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

With no annotations, the description carries the full burden and does so: explicit per-call price ($0.01 USDC via x402), synchronous JSON with no polling, the miss path (404 + payment auto-cancels, 'you only pay for entries that exist'), and the output license (CC0). These are exactly the behavioral traits an agent needs before spending money on a call.

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?

Dense but every clause earns its place: identity, price, cardinality, return contents, failure behavior, and license, all front-loaded. No filler or restatement of the name.

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?

No output schema exists, so the description enumerates the return payload (provenance, creator, license, on-chain pointers/contracts/chains/OpenSea, full CC0 body). Combined with the payment and 404 semantics, an agent has everything needed to call it correctly.

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% for the single `query` parameter, and the resolution order (exact slug → id → fuzzy title) is already documented in the schema description. The tool description adds only the free-text framing, so the baseline 3 applies – the schema does the heavy lifting here.

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 ('agentic read API over cc0pedia') and pins the exact scope: 'get ONE entry resolved from a free-text query'. This cleanly separates it from siblings like cc0pedia-search and cc0pedia-market, which an agent can rule out without opening either 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?

Usage is implied rather than stated: a single-entry lookup from a free-text query. It never names the alternative (cc0pedia-search for browsing, cc0pedia-market, cc0pedia-verify) or the condition that would select one over this, despite four same-prefix siblings existing. The browse URL is a hint, not routing guidance.

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