xero_create_purchase_order

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

Annotations already mark this as non-read-only, destructive, and idempotent, so the description only needs to add context. It adds useful routing and approval context: 'Routes only through the exact project/account governed connector authority' and `approval_ref` is for resuming a write. However, it does not explain what creation does in Xero or what consequences the destructive hint implies; this is adequate but not rich.

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 compact and well-structured: it front-loads identity and routing, then presents a clean labeled list of parameters. The opening line duplicates the tool name, but there is no filler or unnecessary prose.

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?

For a 7-parameter create operation with a critical `arguments` JSON payload, the description is not complete enough for reliable invocation. It lacks any explanation of how to construct a purchase-order payload, what Xero data is required, or what the approval flow entails beyond the `approval_ref` hint. The routing and safety annotations help, but the domain-level semantics 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 description coverage is 0%, so the description must carry the parameter documentation burden. It provides generic one-liners for all parameters, but the most important one, `arguments`, is only described as 'JSON string of arguments for the connector operation' with no expected Xero purchase-order payload, nested line items, or field structure. The routing, idempotency, and approval parameters are clarified, but the core invocation payload remains opaque.

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 opens by restating the tool name as 'Xero connector operation `create_purchase_order`' and 'platform tool `xero.create_purchase_order`' without saying what the operation actually accomplishes. It never states that it creates a purchase order in Xero or describes the resulting resource. The routing sentence adds scope, but the core purpose is left to inference from the 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?

There is no guidance about when to use this tool versus alternatives such as xero_update_purchase_order, xero_create_invoice, or xero_intake_bill. The description lists parameters but provides no context for selecting this operation or excluding others. It is not misleading, but it gives the agent essentially no usage direction.

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