BinanceGetNFTAsset

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

Without annotations, the description carries the full burden. The verb 'Retrieve' strongly implies a read-only operation, but it does not explicitly state side-effect freedom, authentication requirements, or any other behavioral detail. It adds little beyond the obvious, leaving some ambiguity about the operation's safety profile.

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 two sentences, front-loaded with the action 'Retrieve NFT assets', and every sentence adds value. It mentions the return details in the second sentence without fluff or 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?

Despite lacking an output schema and annotations, the description sufficiently explains the tool's purpose and return fields for a simple list operation. The optional parameters are clearly documented in the schema, and the description covers the core functionality. Some minor gaps like authentication context remain, but overall it is reasonably complete.

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 schema already provides 100% description coverage for all three parameters (page, limit, recvWindow). The tool description adds no additional parameter semantics or usage details beyond what the schema states, so it is at the baseline for high schema coverage.

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 uses the specific verb 'Retrieve' to state it fetches NFT assets for a user's account, and lists concrete return details (network, contract address, token IDs). This clearly distinguishes it from sibling tools like NFT deposit/withdraw/transaction history, which focus on different aspects.

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 use when needing a user's NFT asset list, but does not explicitly mention when to avoid it or provide alternatives. There is no direct comparison with sibling tools. The context is present but not fully elaborated, so it earns a mid-tier score.

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