finance_xero_ap_intake_to_pay

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

The annotations indicate destructive and non-read-only behavior, but the description does not explain side effects, what data may be changed, or what the dispatcher invocation entails. It adds only scope context (JWT, tenant, company) and no meaningful behavioral detail.

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 brief and uses a clear structure with an overview and an Args section. It avoids unnecessary wording, though the brevity comes at the cost of semantic content.

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?

Context is incomplete: there are no examples, no indication of expected output, no prerequisites, and no clarification of how this dispatcher action relates to the many similar Xero and finance sibling tools. An agent would struggle to know what objective to provide.

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%, and the description only restates the parameter names: `message` is a 'free-text objective' and `inputs` is an 'optional JSON string'. It does not explain what should go inside the JSON, what objectives are valid, or how the two parameters interact.

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 repeats the tool name and says it 'Runs' the action, but does not state what `xero_ap_intake_to_pay` actually accomplishes or what outcome the agent should expect. It implies an AP intake-to-pay workflow but leaves the real purpose vague.

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 instead of sibling tools such as `xero_intake_bill`, `xero_create_bill`, or other finance domain actions. The description only mentions routing through a dispatcher, not selection criteria.

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