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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Recent transactions' without specifying what recent means, whether transactions are returned in sorted order, pagination limits, or what account format is expected. No details about return values or side effects are given.

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 that is front-loaded and free of unnecessary words. It efficiently conveys the core purpose, though it could benefit from additional details without sacrificing brevity.

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 the absence of an output schema and annotations, the description must explain return values and behavior. It merely states 'Recent transactions' with no indication of what fields are included, how many results are returned, or any other contextual details, leaving the tool under-documented.

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 only defines 'account' as a string, and the description adds only 'Hedera account' as context, which is already evident from the tool name. It does not specify the account format (e.g., '0.0.1234') or any constraints, so the description adds minimal value beyond the schema.

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 'Recent transactions for a Hedera account' clearly identifies the resource (transactions) and the context (a Hedera account), distinguishing it from sibling tools like hbar_account_info or hbar_token_info. However, it lacks an explicit verb such as 'list' or 'retrieve', making it slightly less direct than ideal.

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 usage guidance is provided. The description does not state when to choose this tool over alternatives, nor does it mention any exclusions or prerequisites. The only implied context is that it deals with transactions, but there is no explicit comparison to sibling tools.

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