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

With no annotations, the description carries the behavioral burden and does well: it discloses the paid-x402 model, the exact price ($0.008 USDC on Base), and the resolution strategy across IPFS, Arweave, HTTPS and inline data URIs, plus that the image URL is browser-loadable. Gaps remain around failure behavior for burned/nonexistent tokens and whether metadata fetch failures are surfaced as errors or nulls.

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?

Front-loaded with the resource and an enumerated payload, with the cost/payment detail sensibly placed last. It is a single dense sentence with stacked clauses; every clause carries information, though the return-value enumeration could be tightened without loss.

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?

With no output schema and no annotations, the description compensates by enumerating return fields and the payment requirement, which is what an agent needs to decide and call correctly. Minor shortfall: nothing on error/empty-metadata cases or latency, which matter for a cross-source IPFS/Arweave fetch.

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 both parameters (contract, tokenId) are already documented with patterns, making 3 the baseline. The description adds only the mild constraint that contract is an ERC-721/ERC-1155 collection, which is marginally useful but does not add format, network, or validation detail beyond the schema.

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 (fetch metadata) and resource (ERC-721/ERC-1155 token on Polygon PoS) and enumerates exactly what comes back: collection name, owner, token URI, resolved metadata JSON, and image URL. That level of specificity distinguishes it from the sibling *nft_metadata tools on other chains and from polygon_contract_info / polygon_token_snapshot, which cover different resource types.

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?

Chain scoping ('on Polygon PoS') and the ERC-721/ERC-1155 qualifier implicitly tell the agent when this tool applies, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g. use polygon_contract_info for contract-level data, or polygon_token_snapshot for fungible tokens). Usage is inferred rather than directed.

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