finance_xero_ap_intake_to_pay

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

The description mentions routing through a dispatcher with JWT/tenant/company scope, but does not disclose whether the tool is read-only or write, destructive consequences, side effects, or error conditions. With no annotations, the description carries full burden and fails to provide adequate behavioral context.

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 short and front-loaded with the action name and routing details. The argument definitions are clear and concise. However, it could be improved by adding a brief example or outcome description without significantly increasing 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?

With no annotations and minimal description, the tool lacks contextual completeness. It does not explain return values (despite an output schema existing), intended use cases, or integration with other tools. Important gaps like prerequisites or expected behavior are missing.

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 description must compensate. It adds basic meaning: 'message' is a free-text objective, 'inputs' is optional JSON. However, it lacks details on acceptable formats, constraints, or examples, leaving significant ambiguity.

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 states it runs the finance domain agent action 'xero_ap_intake_to_pay', but does not explain what that action does. The name suggests AP intake to payment, but the description is a tautology that adds no functional clarity. It distinguishes itself from siblings only by name, not by description.

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 on when to use this tool versus other Xero AP tools (e.g., xero_intake_bill, finance_xero_bank_reconciliation). No exclusions, prerequisites, or alternative recommendations are provided.

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