hedera_get_account_by_evm

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions 'via the Mirror Node,' hinting at a read operation, but does not disclose idempotency, authorization requirements, error behavior (e.g., if address not found), or any side effects. This is insufficient for a tool with 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?

The description is a single, direct sentence with no redundant words. It efficiently conveys the core functionality without requiring elaboration.

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 lookup tool with one parameter and no output schema, the description is mostly complete. However, it could optionally hint at the output format (e.g., 'returns account ID and balance') to give the agent full context. Nonetheless, given the tool's simplicity, the description is largely adequate.

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 the evmAddress parameter as '0x-prefixed EVM address' with 100% coverage. The description adds no additional meaning beyond the schema, so it meets the baseline but does not exceed it.

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 'Resolve a Hedera account' from a specific input ('0x EVM address') via a specific method ('Mirror Node'). This verb+resource+scope formulation is precise and distinguishes it from sibling tools like get_account_info which use account IDs.

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?

The description implies usage when you have an EVM address and need the corresponding Hedera account, but it does not explicitly state when to use this tool versus alternatives (e.g., get_account_info for ID-based lookup) or when not to use it. No usage exclusions or context cues are provided.

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