hedera_create_account

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

Describes that the tool 'Build (unsigned)' an account, indicating no immediate blockchain effect. Lacks return format details (probably a transaction object). With no annotations, the description carries full burden but does not fully disclose output.

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 clear sentence, 16 words, no fluff. Front-loaded with purpose.

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?

Adequate for a create tool with full schema coverage, but lacks output format description and does not explain that the new account ID is generated automatically. Slightly incomplete given no output schema.

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 descriptions are complete (100% coverage). Description highlights publicKey and initialBalanceHbar but omits memo, payerAccountId, maxAutomaticTokenAssociations. Baseline 3 with marginal added value.

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?

Description clearly states verb 'Build' and resource 'new Hedera account' with specific inputs (public key, optional HBAR balance). Distinguishes from sibling tools like update/delete account.

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?

Usage is implied for creating new accounts; no explicit when-not or alternatives, but creation tools are self-explanatory. Could mention that the output is unsigned and needs subsequent signing.

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