list_transactions

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

With no annotations, the description carries the full burden but only states that it lists recent transactions. It does not disclose ordering, whether results are limited to the 'recent' window, what constitutes 'recent', or whether it returns all accounts unless filtered. This is minimal but not misleading.

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, front-loaded sentence that states the core purpose without extraneous detail. It includes useful qualifiers (recent, transaction types) and is appropriately sized for a simple list tool.

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 tool with only two optional parameters and no output schema, the description is reasonably complete. It covers the operation and scope, though it leaves the definition of 'recent' ambiguous and does not describe the return format, which is acceptable given the simplicity.

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 the baseline is 3. The description adds no additional meaning about the 'limit' or 'account_id' parameters beyond what is already in the schema, nor does it explain how they affect the 'recent transactions' behavior.

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 identifies the tool as listing recent financial transactions, with a specific verb ('Lista') and resource ('transações financeiras recentes'). It enumerates the transaction types (expenses, gains, transfers), which helps differentiate it from finance siblings like list_finance_accounts or get_finance_summary, though it does not explicitly name alternatives.

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 provides no guidance on when to use this tool versus alternatives such as create_transaction, get_finance_summary, or list_finance_accounts. It does not mention scenarios, exclusions, or prerequisites, leaving the agent to infer appropriate usage from the tool name alone.

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