xero_bank_transactions

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states 'Get' without clarifying if the operation is read-only, what authorization is needed, or any side effects. Critical context like pagination or rate limits is missing.

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 sentence with no fluff, but it is too sparse. While concise, it sacrifices necessary detail. It earns a mid score because brevity alone does not compensate for lack of content.

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 annotations and output schema, and the presence of five parameters, the description is incomplete. It does not explain the purpose of each parameter, return format, or any constraints (e.g., required combinations). The agent has insufficient context to use the tool correctly.

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 provides no information about the five parameters (bank_account_id, date_from, date_to, access_token, tenant_id). With 0% schema description coverage, the description should add meaning but does not, making the agent rely entirely on parameter names which may be ambiguous.

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 'Get bank transactions from Xero' clearly states the action (get) and resource (bank transactions), and identifies the system (Xero). It is specific but does not differentiate from sibling Xero tools like xero_accounts or xero_invoices, which also retrieve data.

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 (e.g., xero_accounts for accounts). The description does not mention prerequisites, filters, or typical use cases, leaving the agent without decision support.

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