xero_list_purchase_orders

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

With no annotations, the description must fully disclose behavioral traits. It only states it lists purchase orders and routing details, but omits idempotency, pagination, filtering, rate limits, or auth requirements beyond JWT/tenant scope. This is insufficient for a list operation.

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 relatively short but includes redundant repetition of the tool name and routing path. The bullet format for arguments is clear, but the information could be more compact while preserving utility.

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?

Although an output schema exists, the description lacks crucial details for using the tool effectively, such as how to format the 'arguments' JSON or what filtering options are available. It does not provide enough context for an agent to invoke this tool correctly.

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 single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation', which adds minimal meaning beyond the schema type. No specification of valid keys, filters, or expected format is provided. With 0% schema coverage, this is a significant gap.

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 lists purchase orders, using the verb 'list' and specifying 'Xero connector operation'. However, it does not differentiate from siblings like 'xero_get_purchase_order' or 'xero_create_purchase_order', leaving ambiguity about when to use this specific tool.

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 vs alternatives. It mentions routing and scoping but lacks instructions on prerequisites, typical use cases, or when not to use it. Given siblings exist, explicit guidelines are missing.

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