xero_create_expense_claim

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

The description notes that it routes through /api/tools/invoke under JWT/tenant/company scope, providing some authentication context. However, without annotations, it fails to disclose critical behavioral traits like whether it has side effects, rate limits, or specific Xero permissions required.

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 and well-structured, with three clear sections. However, the brevity sacrifices informational value.

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 that the tool has only one generic parameter and no output schema, the description should provide more context about what fields are needed and what the response looks like. It is insufficient for an agent to use 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 input schema has a single generic 'arguments' string parameter with no description. The description only repeats that it is a 'JSON string of arguments for the connector operation', offering no meaningful guidance on the expected structure or fields.

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 mentions 'create_expense_claim' and identifies it as a Xero connector operation, making the basic purpose clear. However, it does not differentiate this from sibling tools like xero_update_expense_claim 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?

No guidance is provided on when to use this tool versus alternatives such as xero_update_expense_claim. There is no mention of prerequisites, typical use cases, or when not to use it.

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