hedera_get_nft_history

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

Description indicates read-only operation, but lacks details on Mirror Node data freshness, rate limits, or response structure. Without annotations, more transparency would be beneficial.

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?

Single sentence, 15 words, front-loaded with key information. No extraneous content.

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?

Lacks details on return value (array of transfers), pagination, or error conditions. No output schema to compensate, leaving the agent underinformed.

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?

Description mentions 'specific NFT serial' and 'transfer/mint history' hinting at parameters, but does not explicitly describe tokenId format or serial constraints. With 0% schema description coverage, it fails to compensate.

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 it reads transfer/mint history of a specific NFT serial from the Mirror Node, using a specific verb and resource. It distinguishes from sibling tools like hedera_get_nft_info (current info) and hedera_get_token_nfts (list of 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?

No guidance on when to use this tool versus alternatives. For example, it does not explain when to prefer this over hedera_get_nft_info or other history tools.

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