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

With no annotations, the description carries the full load and does disclose two important traits: a paid x402 call ($0.008 USDC on Base) and external fetching from IPFS/Arweave/HTTPS/data URIs, implying latency and possible upstream failures. It omits what happens when metadata resolution fails or is missing, keeping it short of a 5.

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?

A single dense sentence, front-loaded with the purpose then the return contents then the cost. Every clause carries information, though the run-on structure with a long appositive slightly hurts scannability.

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, the description effectively documents the return shape (collection name, owner, token URI, decoded metadata JSON, image URL), which is what an agent needs. Missing only edge-case behavior (missing/broken metadata, ERC-1155 owner semantics) to reach a 5.

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% with both parameters fully documented (decimal tokenId pattern, contract address pattern). The description adds no parameter-level detail beyond 'on Arbitrum One', so baseline 3 is appropriate.

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 resource (ERC-721/ERC-1155 token metadata) scoped to a specific chain (Arbitrum One), and lists the exact fields returned. An agent can distinguish it from arbitrum_contract_info or arbitrum_token_snapshot by the NFT-specific output described.

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 by the content ('NFT metadata'), but there is no explicit when-to-use or when-not-to-use guidance relative to siblings like arbitrum_contract_info or eth_nft_metadata (chain choice). The agent must infer selection from the chain scope alone.

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