xero_bank_transactions

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states a read operation but does not convey potential side effects, authentication requirements, pagination, rate limits, or what happens if parameters are omitted. For a read tool, this is insufficient.

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 extremely concise (5 words) but at the cost of completeness. It is not well-structured for an agent, as it omits essential details that should be front-loaded. This qualifies as under-specification rather than efficient conciseness.

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 tool has five parameters, no schema descriptions, no annotations, and no output schema, the one-sentence description is wholly inadequate. It fails to inform the agent about parameter usage, return values, or required context for invocation.

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 has five parameters (bank_account_id, date_from, date_to, access_token, tenant_id) with zero descriptions. The description does not explain any parameter's meaning or usage, failing to compensate for the 0% schema coverage. This is a complete lack of semantic guidance.

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 verb 'Get' and the resource 'bank transactions from Xero'. It distinguishes from sibling Xero tools like xero_accounts or xero_invoices, which deal with different data. However, it does not provide additional context about scope or filtering.

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 on when to use this tool versus alternatives (e.g., other Xero tools) or prerequisites such as authentication or required parameters. The description simply states the action without context.

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