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

No annotations are provided, so the description carries the burden. It discloses the return contents (image URL, attributes, storage properties) and storage location (IPFS or Warren on-chain), which is useful. However, it does not mention side effects or error behavior, and the terms 'looksmaxxed' and 'Warren on-chain' are unexplained, leaving some ambiguity.

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, front-loaded sentence that efficiently conveys the core purpose and key output details. There is no redundant information or filler, earning a top score.

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 getter with one parameter and no output schema, the description is reasonably complete: it states what is returned and mentions image storage types. However, it lacks context about what 'looksmaxxed' means, potential failure modes, and whether it works for all ERC-721 NFTs or only a specific collection. This slight gap prevents a 5.

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 description coverage is 100%, with tokenId described as 'NFT token ID (numeric string)'. The description adds no additional parameter meaning beyond stating it is for a 'looksmaxxed NFT', which is a collection-level qualifier rather than a parameter detail. Baseline 3 applies because the schema fully documents the parameter.

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 'Returns ERC-721 metadata for a looksmaxxed NFT' with specific contents (image URL, attributes, storage properties). This distinguishes it from siblings like get_nft_inventory, which likely returns a list of owned NFTs, and get_gallery, for a gallery view.

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?

Usage context is implied: the tool is for fetching metadata for a specific NFT (by tokenId). However, there is no explicit guidance on when to use this vs. siblings, such as 'use get_nft_inventory to list NFTs first' or 'use this for metadata only'. No exclusions or alternatives are mentioned.

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