hedera_create_nft_collection

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

No annotations are provided, so the description carries full burden. It discloses that the tool builds an unsigned transaction and that a supply key is required to mint. However, it does not explain that the returned transaction must be signed and submitted separately, nor does it mention side effects, authorization needs, or error conditions.

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?

Two sentences with no wasted words. The key information (builds NFT collection, unsigned, supply key required) is front-loaded. Could benefit from slightly more structure (e.g., listing required keys), but overall efficient.

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?

With 12 parameters, no output schema, and no annotations, the description is too brief. It does not explain the overall workflow (that the tool returns an unsigned transaction that needs to be signed), the role of keys (admin, supply, treasury), or the royalty fee configuration. For a complex tool, this is inadequate.

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 42% (low), and the description adds minimal semantic value beyond the schema. It only reinforces that supplyKey is required for minting. No explanation of key parameters like adminKey, treasuryAccountId, royalty fields, or their relationships. The description fails to compensate for the low 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 clearly states it builds a new NFT collection (non-fungible token) on Hedera Token Service (HTS) and identifies it as unsigned, distinguishing it from sibling tools like hedera_mint_nft, hedera_burn_token, etc.

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 explicit guidance on when to use this tool versus alternatives like hedera_create_fungible_token or hedera_mint_nft. Only mentions supply key requirement for minting, but lacks when-not-to-use or contextual triggers.

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