get_account_info

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

No annotations are provided, so the description carries the full burden. It does disclose the underlying RPC call (kaia_getAccount), which is useful transparency, but 'Get' only implicitly signals a read-only operation and there is no mention of permissions, rate limits, or error behavior.

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?

A single efficient sentence that is front-loaded with the resource and includes the RPC method without padding. Nothing superfluous, though the RPC method name is somewhat niche for the primary audience.

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 simple read tool with two fully-documented parameters and no output schema or annotations, the description compensates by enumerating the returned fields. The remaining gap is sibling disambiguation against get_kaia_balance.

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 description coverage is 100%, so both the address and optional network parameters are already documented in the schema. The description adds no parameter-level meaning (the parenthetical lists return fields, not inputs), so the baseline 3 applies.

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?

States a specific verb+resource (get account info) and enumerates the returned fields (type, balance, nonce, accountKey) plus the underlying RPC method kaia_getAccount. It is clear but does not distinguish itself from the closely related sibling get_kaia_balance, which an agent could easily confuse with the balance field listed here.

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?

There is no guidance on when to use this tool versus alternatives such as get_kaia_balance or get_account_tokens. Usage is only implied by the field list, leaving the agent to infer the choice.

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