freeagent_list_bank_transactions

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

No annotations are provided, so the description must cover behavioral traits. It only states the basic action. It does not disclose pagination, rate limits, authentication needs, or what happens when parameters are invalid. For a list operation, it lacks details about response format or potential size limits.

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 with the key action. No unnecessary words or repetition. It efficiently conveys the core purpose.

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 lack of output schema and annotations, the description is minimal. It does not explain pagination, default filters, or response structure. For a list tool with multiple optional parameters, additional details like 'Returns a list of transactions' or 'Use from_date/to_date for date range' would improve completeness, but the description is adequate for basic understanding.

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 coverage is 100%, so the input schema already provides parameter descriptions. The tool description does not add any additional meaning beyond what the schema states. Baseline 3 is appropriate as the schema does the heavy lifting, and the description offers no extra context.

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 'List bank transactions from FreeAgent for a specific bank account', which identifies the verb ('List'), resource ('bank transactions'), and scope ('for a specific bank account'). This distinguishes it from siblings like freeagent_get_bank_transaction (single transaction) and freeagent_list_bank_accounts (different resource).

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 freeagent_get_bank_transaction for a single transaction. It does not mention prerequisites or conditions for use, leaving the agent to infer from the name and siblings.

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