fetch_nft_metadata

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It mentions 'fetch and parse' which implies network access and parsing, but it does not disclose that this is a read-only operation, possible failure modes (e.g., invalid token URI), or whether the metadata is returned as raw JSON or parsed fields. This is insufficient without annotation support.

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 a single concise sentence, front-loaded with the action. It is appropriately sized for the tool's simplicity and wastes no words, providing the essential information in eight words.

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?

Given the absence of an output schema and annotations, the description does not fully cover what the agent needs to know. It does not mention the return value format, error handling, or special cases like non-standard metadata. The presence of many sibling NFT tools makes this brevity a gap, as the agent cannot infer whether this tool returns on-chain data vs. parsed URI content.

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 already provides descriptions for all three parameters (network, tokenId, collectionAddress), giving 100% schema coverage, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema provides; it does not clarify how the token URI is derived or any constraints on the parameters.

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 verb 'Fetch and parse' and the resource 'NFT metadata from its token URI', making the tool's function unambiguous. However, it does not explicitly differentiate from similar sibling tools like get_nft_info or get_erc1155_token_metadata, which may also return metadata.

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 provides no guidance on when to use this tool versus alternatives, such as when to prefer it over get_nft_info or get_nft_collection_info. There is no 'when to use' or 'when not to use' context, leaving the agent without direction given the large pool of NFT-related sibling tools.

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