xero_list_bank_transactions

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

The description contradicts the input schema by labeling bank_account_id as 'required' when the schema defines it as optional (nullable with default null). This is misleading and harmful. No other behavioral traits (pagination, filtering limitations, permissions) are disclosed.

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 relatively concise and front-loaded with the primary purpose, but the inclusion of a misleading 'required' label detracts from clarity. The structure (short sentence followed by Args list) is acceptable but could be tighter.

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 list tool with an output schema, the description does not mention pagination, the scope of results, or what happens when optional parameters are omitted. The optionality discrepancy further reduces completeness. It minimally covers the function.

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 description adds helpful parameter details (e.g., 'Start date (YYYY-MM-DD)') beyond the schema's minimal titles, but the incorrect 'required' label for bank_account_id undermines reliability. Schema coverage was 0%, so some value is added, but the error reduces the score.

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-feed transactions on a Xero bank account,' specifying a concrete verb and resource. It distinguishes itself from sibling tools like xero_list_invoices or xero_list_payments by focusing on bank-feed 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?

No guidance is provided on when to use this tool versus alternatives, nor are there exclusions or context for choosing it over other list tools. The description lacks any 'use this when' or 'consider X instead' advice.

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