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

Goes well beyond the annotations: describes the 422-uncharged path for nonexistent tokens, metadataError for unreachable metadata, truncation of strings over 1,000 characters (on-chain SVGs), the ipfs.io gateway, and per-call pricing with the first 25 free. It is consistent with readOnlyHint=true and idempotentHint=false ('each call is charged, so repeats are not free'). Minor gap: doesn't say whether a partially resolved JSON is returned alongside metadataError.

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 front-loaded: purpose and return shape first, routing and error semantics next, pricing last. The pricing/free-tier sentence is somewhat boilerplate for a per-call tool but is operationally relevant; no sentence is pure filler.

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 still tells the agent exactly what comes back (tokenURI plus name/description/image/attributes) and how failures surface (422 uncharged, metadataError). Nothing needed to call or interpret the result is missing.

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%, so baseline is 3; the description adds a concrete worked example (contract=0x943e..., tokenId=1) that shows the expected address casing and a numeric id, which is more than the schema alone conveys. It doesn't document the odd accepted types for tokenId, but the schema covers that.

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?

Names a specific verb and resource: reads the tokenURI of one ERC-721 token id on Unichain plus the JSON it resolves to (name, description, image, attributes). It explicitly distinguishes itself from the sibling unichain_nft_owner, so an agent can choose correctly without opening a 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?

States the use case directly ('Use to show or check what an NFT is') and names the alternative for the adjacent task ('for its owner use unichain_nft_owner'). It also sets cost/charge expectations that affect whether an agent should call it repeatedly.

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