hedera_get_account_info

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

The description indicates a read operation from the Mirror Node, implying no state modification. However, it does not detail data freshness, rate limits, or public access nature. The behavioral disclosure is basic but adequate given no annotations.

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. Front-loads purpose and lists key fields. No unnecessary content.

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?

Description covers purpose, source, fields. Lacks expected output format or structure, but for a simple read tool with one parameter, it is mostly complete.

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 coverage is 100%, baseline 3. The description does not add meaning beyond the schema's 'Account id or EVM address'. No extra context or constraints provided.

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 uses a specific verb 'Read' and clearly states the resource 'full account info' listing key fields like key, balance, memo, auto-renew, associations. It distinguishes this tool from siblings like hedera_get_account_balance which only retrieves balance.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention when to prefer this over hedera_get_account_balance or other related tools.

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