xero_pay_bill

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

Annotations are absent, so the description must disclose behavioral traits. It mentions routing under JWT/tenant/company scope, which is helpful, but it fails to state key aspects such as whether the operation is destructive, what side effects occur (e.g., invoice status change), or what the return value contains.

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, but it is not concise in a value-adding sense—it omits essential details. It is adequately structured but incomplete.

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 paying a bill in Xero and the lack of annotations or meaningful parameter documentation, the description is far from complete. It does not explain what the tool does, how to structure the arguments, or what the output schema contains.

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 only parameter 'arguments' is a JSON string with default '{}'. The description simply says 'arguments for the connector operation', adding no meaning beyond the schema. With 0% schema description coverage, this is insufficient.

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 identifies the tool as 'pay_bill' but offers no elaboration on what paying a bill entails in Xero. The name implies the purpose, but it does not distinguish from similar sibling tools like xero_create_payment or xero_list_payments.

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 versus alternatives. With many Xero payment-related tools available (e.g., xero_create_payment, xero_create_bill), the agent lacks context to select this tool appropriately.

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