hedera_token_airdrop

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

States it builds an unsigned transaction and auto-associates recipients, but lacks details on permissions, side effects, or further steps. With no annotations, this is adequate but not comprehensive.

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, 13 words, efficient and front-loaded with key information.

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?

Covers core functionality and auto-association, but lacks output format (e.g., returns unsigned transaction bytes) and error cases. No output schema to rely on.

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 adds no parameter-specific meaning; the schema already covers 'amount' and 'fromAccountId'. With 40% schema coverage, the description should compensate but does not explain tokenId or toAccountId.

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 an unsigned fungible-token airdrop and highlights the key auto-association feature. It distinguishes from sibling tools like hedera_transfer_token or hedera_associate_token.

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 vs alternatives like hedera_transfer_token. Does not mention prerequisites or use cases.

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