get_erc1155_token_metadata

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

No annotations are provided, so the description is the sole source of behavioral info. It adds that metadata 'typically points to JSON metadata,' which hints at the return format but leaves ambiguity about whether the tool returns the URI or the resolved JSON. No error behavior or network defaults are mentioned.

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 concise with two sentences, front-loaded with the action. The second sentence provides useful context about the ERC1155 standard without any fluff.

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 should clarify the return value more thoroughly. It leaves critical ambiguity about whether the output is a token URI or the actual JSON metadata, and lacks details on network behavior or failure cases.

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 input schema covers 100% of parameter descriptions, so the baseline is 3. The description does not add additional parameter semantics beyond what the schema already provides (e.g., tokenId, tokenAddress, network).

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 states the tool fetches metadata for an ERC1155 token and explains the token standard. However, it doesn't explicitly distinguish from sibling tools like 'fetch_nft_metadata' or 'get_nft_info'.

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 the tool is used when ERC1155 metadata is needed but provides no explicit when/when-not guidance or alternatives. The name and standard clarification give some context, but there's no comparison to other NFT metadata tools.

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