hedera_update_account

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

The description discloses that the tool builds an unsigned transaction, which is a key behavioral trait. However, with no annotations, it omits details about authorization requirements, side effects, or reversibility. The unsigned nature is a partial disclosure.

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 very short (one phrase), which is concise but at the expense of completeness. It front-loads 'Build (unsigned)' but offers no structure or additional details.

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 no output schema and low schema coverage, the description leaves significant gaps. It does not explain return value, prerequisites, or the need to sign/submit after building. For a mutation tool, this is insufficient.

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?

The description adds meaning by naming 'memo' and 'auto-association slots' corresponding to memo and maxAutomaticTokenAssociations parameters. However, accountId and payerAccountId are not elaborated beyond the schema, and payerAccountId's role remains unclear. With low schema coverage (25%), the description partially compensates.

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 states it builds an unsigned account update for memo and auto-association slots, which is specific and distinguishes it from other Hedera tools. However, the term 'Build (unsigned)' might imply it doesn't execute the update directly, which could be clarified further.

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_update_token or hedera_delete_account. The description does not specify prerequisites or exclusions.

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