finance_xero_reconciliation_review

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

No annotations are provided, so the description carries the full burden. It discloses that this is a domain agent action rather than a direct API call and mentions authentication scope, but it does not specify side effects (e.g., whether it is read-only or mutates data), rate limits, or failure behavior. The behavioral disclosure is moderate.

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 concise, with four sentences including the Args list. The main purpose is front-loaded, and there is no extraneous information. It is efficiently structured, though it could be slightly more informative without adding length.

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?

Despite having an output schema (reducing the need to explain return values), the description is vague about what the reconciliation review actually entails (e.g., matching transactions, flagging discrepancies). For a domain agent action, more context about the review process would help the agent select and invoke it 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?

Schema description coverage is 0% (no parameter descriptions in the schema), so the description must compensate. It provides basic descriptions for the two parameters ('Free-text objective' and 'Optional JSON string of structured inputs'), adding some meaning beyond the schema's title and type. However, the descriptions are minimal and lack details like expected format or constraints.

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 that the tool runs the finance domain agent action 'xero_reconciliation_review', which is a specific verb+resource combination. The name and description together convey the purpose, though sibling differentiation is not explicit but implied by the unique name.

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 mentions routing through the domain-agent dispatcher under JWT/tenant/company scope, which implies when to use this tool (i.e., when triggering a finance agent action for Xero reconciliation). However, it does not provide explicit guidance on when not to use it or alternatives among the many sibling Xero tools.

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