finance_xero_bank_reconciliation

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions auto-matching and surfacing ambiguous matches but does not indicate whether the tool modifies data, requires permissions, or has any destructive or irreversible effects. This is insufficient for a reconciliation tool.

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: one sentence for core behavior followed by a parameter list. It is front-loaded with the key action and contains no unnecessary words. Every line earns its place.

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's complexity and existence of an output schema, the description covers the core reconciliation function but lacks details on confidence thresholds, output format, side effects, or failure modes. It is minimally complete but leaves gaps.

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 0%, so the description must add meaning. It defines each parameter: message as free-text objective, account_id with behavior when empty (all accounts), and date formats. This adds significant value beyond the schema's minimal titles and defaults, though the message's purpose could be clearer.

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 reconciles Xero bank-feed transactions against the ledger, with auto-matching for high confidence and surfacing ambiguous matches for review. This distinguishes it from siblings like finance_reconciliation_exceptions and finance_xero_reconciliation_review.

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 implies the tool is for reconciliation but does not explicitly state when to use it versus alternatives like finance_reconciliation_exceptions or finance_xero_reconciliation_review. No when-not-to-use guidance is provided.

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