freeagent_list_transactions

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

Annotations already indicate read-only and non-destructive behavior. The description adds valuable context: default returns unexplained transactions, details on returned fields, and reconciliation workflow. No contradiction with 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?

Extremely concise: two sentences plus a clear instruction. The main action and default are front-loaded. Every sentence contributes value without redundancy.

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?

Despite no output schema, the description explains return fields (id, date, description, amount, explanation details) and provides essential workflow guidance for reconciliation. Completes the picture 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?

The input schema provides 100% description coverage for all parameters. The description adds minimal extra meaning beyond the schema (e.g., noting bankAccountId comes from list_bank_accounts). Baseline 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 states the tool lists bank account transactions from FreeAgent, specifying the default (unexplained) and linking to bankAccountId from a sibling tool (freeagent_list_bank_accounts). This differentiates it from other actions like creating expenses or explaining transactions.

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?

It provides clear context on default behavior and offers workflow guidance for reconciliation tasks, instructing the agent to search email/file sources before asking the user. However, it lacks explicit when-not-to-use instructions or direct comparison with all siblings.

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