hedera_get_nft_info

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

With no annotations, the description carries full burden. It correctly indicates a read-only operation via 'Read' and mentions the data source (Mirror Node) and expected fields. However, it does not disclose potential behaviors like rate limits, caching, data recency, or any other side effects. The description is minimally adequate.

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 efficient sentence that starts with the action and resource. No redundant words. However, it could be slightly improved by incorporating basic parameter explanations without becoming verbose.

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?

No output schema exists, so the description is the sole source for output expectations. It lists owner, metadata, serial but omits other potential fields and doesn't specify structure or format. For a read tool with only 2 parameters, more context is needed to set complete expectations.

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 0%, so the description must compensate but fails to. It does not explain what tokenId or serial represent or provide any format hints. While parameter names are self-explanatory, the description adds no context about expected values (e.g., token ID format, serial range).

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 a specific verb 'Read' and specifies the resource 'a specific NFT's info' with examples of data returned (owner, metadata, serial). It clearly distinguishes from sibling tools like hedera_get_token_nfts (list) and hedera_get_nft_history (history), making the tool's purpose unambiguous.

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 usage when one needs information about a single NFT with known tokenId and serial, but it does not explicitly state when to use this tool versus alternatives like hedera_get_token_nfts or hedera_get_nft_history. No explicit 'when not to use' or comparative guidance.

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