nft-metadata

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

No annotations are provided, so the description carries the full burden. It details the returned fields (name, description, traits, image URL, floor price, etc.) and supported networks. It does not disclose potential rate limits or data freshness, but is otherwise transparent about what the tool does.

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, well-structured paragraph with three sentences that front-load the action and list returns, supported networks, and use cases. Every sentence adds value, and there is no redundancy.

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 straightforward fetch tool with no output schema, the description adequately explains the return fields and scope. It lacks details on error handling or data freshness, but covers the essential information for an AI agent to use the tool correctly.

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%, meeting the baseline. The description adds minimal parameter semantics beyond the schema; it restates contract format and token ID type but does not clarify the network options inconsistency (description lists support for Arbitrum but not Optimism, while schema includes optimism).

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 the resource 'NFT metadata, traits, image URL, and collection floor price' for ERC-721 and ERC-1155 tokens. It is specific and distinguishes from siblings by focusing on generic NFT metadata, but does not explicitly differentiate from other NFT tools.

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 use cases ('NFT valuation research, portfolio analysis') and indicates broad applicability. However, it does not mention when not to use this tool or suggest alternatives among sibling tools.

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