hedera_delete_account

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

With no annotations provided, the description carries full burden. It discloses the 'unsigned' nature of the built transaction, which is a key behavioral trait, but does not fully describe implications such as irreversibility, required authorization, or potential errors. Additional context would improve transparency.

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, clear sentence with no redundant words. It efficiently communicates the core purpose and action.

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?

For a potentially dangerous operation (account deletion), the description is minimal. It lacks safety context, prerequisites, and details about the unsigned transaction output. Without annotations or an output schema, more information is needed for safe use.

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 input schema already describes accountId and transferAccountId with simple labels. The tool description adds no extra parameter guidance. With 67% schema coverage, the description does not compensate for the undocumented payerAccountId parameter.

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 the action ('Build an account deletion') and the critical behavior ('transferring the remaining balance to another account'). It distinguishes itself from sibling deletion tools by specifying the resource and the balance transfer aspect.

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_account or hedera_transfer_hbar. It does not mention prerequisites or contraindications.

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