hedera_get_token_nfts

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 mentions listing serials from the Mirror Node but lacks details on pagination (limit is documented in schema but not explained), whether it returns metadata, or any rate limits. The description is too terse to adequately inform behavior.

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 (one sentence) and front-loaded. However, it sacrifices necessary detail for conciseness. Every sentence should earn its place; here, it is too brief to be fully useful.

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 no output schema, no annotations, and zero schema descriptions, the description is incomplete. It does not explain pagination, return format, or parameter meanings. A simple list tool still needs basic contextual details.

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 0%, so the description must compensate. It indirectly implies tokenId is the collection ID but does not explain the limit parameter or provide any parameter-specific guidance. The description adds no semantic value beyond what the schema shows.

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 'List', the resource 'minted NFTs (serials) of an NFT collection', and the source 'from the Mirror Node'. It distinguishes from sibling tools like hedera_get_nft_info (single NFT) and hedera_get_account_nfts (account-owned NFTs).

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 does not provide any guidance on when to use this tool versus alternatives, nor does it specify prerequisites (e.g., tokenId must be an NFT collection ID). It only implies usage by stating what it does, but no explicit when-to-use or when-not-to-use information.

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