xero_update_expense_claim

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

Annotations already communicate readOnly=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the description does not need to repeat those. It adds useful context about governance routing and the approval_ref requirement for resuming writes, which goes beyond the annotations. However, it does not describe potential side effects of updating an expense claim or what happens to existing claim data.

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 compact and uses a clear bulleted parameter list without redundant prose. Each line earns its place. It could be improved by front-loading the actual business purpose instead of beginning with a restatement of the tool name.

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?

This is a mutation tool with an opaque `arguments` JSON payload, no parameter descriptions in the schema, and no explicit statement of what fields or values the Xero update operation expects. The description explains the platform wrapper well but is not self-sufficient for an agent to know how to construct a valid update_expense_claim call. Output schema presence helps returns but not input construction.

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 description coverage is 0%, so the description carries the full burden for parameters. It provides meaningful one-line semantics for all seven parameters, including project_id, connector_account_ref, idempotency_key, effect, and approval_ref. The main weakness is that `arguments` is described only as a 'JSON string of arguments for the connector operation', leaving the actual update payload undocumented.

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 mostly restates the tool name: "Xero connector operation `update_expense_claim`" adds no functional meaning beyond the name itself. It never explicitly states that this tool updates an existing Xero expense claim, and it does not differentiate itself from related tools like xero_create_expense_claim, xero_update_receipt, or xero_list_expense_claims.

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 gives no guidance about when to use this operation versus alternatives. The phrase "Routes only through the exact project/account governed connector authority" is a routing constraint, not usage guidance. There are no stated exclusions, prerequisites, or conditions like 'use this to modify an existing claim that was previously created'.

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