nft_metadata

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

With no annotations, the description carries the full burden for behavioral transparency. It mentions pricing and an API endpoint but does not disclose whether the tool is read-only, any rate limits, authentication needs, or potential side effects. The behavior is implied to be a query but not explicitly stated.

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 very short and front-loaded with the purpose. It includes pricing information and a link, but lacks a structured format (e.g., bullet points). It is concise but could be slightly more organized without adding unnecessary length.

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?

Despite having no output schema, the description fails to explain what the tool returns or what information is included in the metadata. It leaves the agent without sufficient context about the response format or content, which is critical for a query tool.

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 clear descriptions for both parameters (tokenAddress and tokenId) with 100% coverage. The description adds no additional meaning, format constraints, or examples beyond the schema, so it merds a baseline score of 3.

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 explicitly states 'NFT元数据查询' (NFT metadata query), clearly indicating the tool's function. It distinguishes from sibling NFT tools like nft_floor, nft_owner, and nft_trades, which perform different operations.

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 its siblings. No mention of context, prerequisites, or alternatives, leaving the agent to infer usage without explicit direction.

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