hedera_get_account_transactions

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

The description implies a read operation but does not disclose behavioral traits such as pagination, ordering, or what constitutes 'recent'. With no annotations provided, the description bears the full burden, yet it adds minimal behavioral context beyond the tool's name.

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 concise sentence, but it is too brief to be fully helpful. While it avoids fluff, it sacrifices necessary detail, making it adequate but not well-structured for informative use.

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?

Given no output schema, 0% schema description coverage, and many sibling tools, the description is incomplete. It fails to specify output format, limit behavior, or how results are ordered, leaving significant gaps for the agent.

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 0%, and the description makes no mention of the 'accountId' or 'limit' parameters. It only hints at 'account' but does not explain required format, defaults, or constraints, leaving the agent without guidance.

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 tool lists transactions for an account from the Mirror Node, specifying the verb 'list', the resource 'transactions', and the source 'Mirror Node', which distinguishes it from sibling tools like hedera_get_account_info (account details) and hedera_get_transaction (single transaction).

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 on when to use this tool vs alternatives. For example, it does not clarify when to use this over hedera_get_transaction or hedera_get_contract_results, nor does it mention any prerequisites or contexts where this tool is appropriate.

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