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

With no annotations, the description carries the full burden for behavioral disclosure. It indicates the kind of data returned (balance, key type, token holdings) but does not explicitly state that this is a read-only operation, whether errors are possible for invalid accounts, or any other side effects or limitations. The description is a fragment, not a full behavioral statement.

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 extremely concise, using a simple list to communicate the core purpose. Every word earns its place, and the structure is front-loaded with the most important information. There is no redundant or filler 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?

For a simple tool with one parameter and no output schema, the description lists the main data points returned without explaining the return structure or error handling. It is minimally adequate for an agent to infer the tool's function, but it lacks explicit mention of whether it returns a flat object or something more complex. However, the scope is narrow and the description is not misleading.

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 provides a complete description of the 'account' parameter with an example format. The tool description adds no additional parameter semantics, but schema coverage is 100%, so the baseline of 3 is appropriate.

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 indicates that the tool provides account-level information about a Hedera account, specifically balance, key type, and token holdings. It distinguishes itself from sibling tools like hbar_token_info and hbar_transactions by focusing on account attributes rather than token-specific data or transaction history.

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 is provided on when to use this tool versus alternatives. The description simply lists the data fields returned and does not mention any context, prerequisites, or exclusions. Sibling tools are not referenced, and there is no 'when to use' language.

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