hedera_transfer_token

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

No annotations are provided, so the description must fully disclose behavior. It states 'Build (unsigned)' but does not explain what 'build' means operationally (e.g., returns a serialized transaction, requires subsequent signing), nor does it describe any side effects, permissions, 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?

The description is a single concise sentence with no extraneous words. It is front-loaded with the core action. However, it could include slightly more detail without sacrificing brevity.

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 the presence of 5 parameters and no output schema, the description is insufficient. It does not clarify the return value, the fact that the tool does not execute the transfer, or how to use the result. Sibling tools offer similar operations but differentiation is lacking.

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?

With only 40% schema description coverage, the description does not add any parameter-specific details beyond what is in the schema. Critical parameters like tokenId, toAccountId, and payerAccountId lack semantic explanation.

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 specifies the verb 'Build', the resource 'fungible token transfer', and adds the qualifier 'unsigned', distinguishing it from related tools. It clearly identifies the action and scope of the tool.

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 like hedera_transfer_nft or hedera_transfer_hbar. Prerequisites (e.g., token association) and scenarios are not mentioned.

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