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

Annotations cover read-only and open-world traits, and the description adds genuinely useful behavior beyond them: the tool is paywalled ($0.005 USDC on Base via x402) and it will resolve URIs across IPFS, Arweave, data URIs and https, which signals possible resolution failures or latency. It does not contradict the annotations.

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 that front-loads the resource and output, followed by a short payment clause. No filler, and the price is the single most consequential operational fact for an x402 tool.

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 correctly enumerates the return shape (token URI plus resolved name, image, attributes) and flags the paid invocation path. Remaining gaps are parameter format and sibling routing rather than missing return or safety information.

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% for both required params, so the description carries the full burden. It conveys that a contract and token are involved and constrains the contract to ERC-721/ERC-1155, but never states that contract is a 0x address or that tokenId is a decimal string, leaving the pattern-only schema unexplained.

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: resolves NFT metadata (token URI, name, image, attributes) for an ERC-721/ERC-1155 token on Base. Clear scope, but it never names or contrasts with the closely related sibling base_nft_owner or base_token, so an agent must infer the split itself.

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?

No when-to-use guidance, prerequisites, or alternatives are given. It implicitly says 'call this when you need metadata', but nothing distinguishes it from base_nft_owner (ownership) or base_token, both of which an agent could plausibly pick for the same contract/tokenId pair.

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