finance_xero_reconciliation_review

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

Annotations already indicate destructive and open-world hints. The description adds no additional behavioral context (e.g., specific mutations or side effects), but it does not contradict the annotations either. Given the annotations present, the description contributes no extra transparency.

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 succinct and well-organized, with a clear statement of action, routing context, and argument list. No unnecessary details or redundancy.

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?

The description names the action but does not explain what reconciliation review entails, nor does it provide context about the action's purpose or behavior. While output schema exists and return values need not be described, the fundamental question of what the action does is left unanswered, making the description incomplete.

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 schema has no parameter descriptions, but the description provides brief meaning: 'message' is a free-text objective and 'inputs' is optional JSON structured inputs. This gives some semantic information but lacks specifics like expected keys or formats, so it only partially compensates for the missing schema descriptions.

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 runs a specific finance domain agent action named `xero_reconciliation_review`, providing a specific verb and resource. However, it does not explain what that action does, nor does it differentiate from sibling Xero tools, so it falls short of full clarity.

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 offers no guidance on when to use this tool versus alternatives. It merely states the action name and routing, with no indication of scenarios or conditions favoring this tool over sibling Xero functions.

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