xero_create_purchase_order

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions authentication scope (JWT, tenant, company) and routing. There is no information about side effects (e.g., does it create a record immediately? Is it idempotent?). The description fails to convey what happens upon invocation beyond the name.

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 very short but lacks valuable content. It repeats the tool name and mentions routing, but the 'Args' line is out of place and adds little. Every sentence should provide useful information; these do not. The description is under-specified rather than concise.

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?

Given the complexity of a purchase order operation, the description is severely incomplete. There is no information about required fields (e.g., supplier, line items), output format (despite having an output schema, it is not described), prerequisites, or error handling. The agent cannot use this tool effectively without external knowledge.

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 input schema has a single string parameter 'arguments' with no sub-schema or description. Schema description coverage is 0%. The description says 'JSON string of arguments for the connector operation' which is vague and provides no details about the expected structure, required fields, or example values. This is insufficient for an agent to construct valid input.

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 tool name 'create_purchase_order' clearly indicates it creates a purchase order. The description adds 'Xero connector operation' which reinforces the domain but does not distinguish it from sibling create operations like xero_create_bill or xero_create_invoice. No specific scope or differentiation is provided, but the verb+resource is clear.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, context, or exclusions. The agent is left without any hint about appropriate use cases.

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