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

Beyond the readOnly/idempotent hints, the description discloses valuable behavioral details: the `{id}` substitution is left visible, the URI is returned as text, the tool never fetches the URL itself, there is a $0.001 USDC cost, supported chains are listed, and results are byte-identical to a specific REST endpoint. This significantly exceeds the annotation baseline.

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?

The description is compact and front-loaded with the most important semantic detail, then adds cost, chains, and an exact REST-equivalent reference. Every sentence contributes actionable information without 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?

For a simple read-only ERC-1155 URI lookup, the description covers the output form, behavioral guarantee of not fetching, cost, supported chains, and REST equivalency. The output schema exists, and annotations cover safety/idempotency, so nothing critical 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?

The schema already covers all three parameters with clear descriptions at 100% coverage, so the baseline applies. The description adds a concrete endpoint example and reiterates chain keys, but it does not substantially deepen parameter meaning beyond what the schema and example already convey.

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 clearly identifies the tool's action: decoding `uri(id)` from the ERC-1155 ABI and returning the metadata URL a wallet would fetch. It is specific about the resource and output format, and the title plus supported-chain list distinguish it from ERC-721-oriented sibling tools like `chain_nft_token_uri`.

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?

The description implies when to use this tool—when you need the metadata URL for a token ID without fetching it—and clarifies that the tool never requests the URL. However, it does not explicitly direct users to alternative sibling tools (e.g., `chain_nft_token_uri` for ERC-721) or state when not to use it, leaving some routing to inference.

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