xero_list_repeating_invoices

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

No annotations provided. The description mentions routing details (JWT, tenant, company scope) but fails to disclose behavioral traits such as whether the operation is read-only, pagination behavior, or rate limits.

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 and avoids verbosity, but it lacks substantive information. It is not concise in a helpful sense; it is merely sparse.

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?

Despite having an output schema, the description does not explain the tool's core functionality effectively. The opaque 'arguments' parameter is left unexplained, making the tool hard to use 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 only parameter 'arguments' is described as 'JSON string of arguments for the connector operation' without any detail on expected keys or format. Schema coverage is 0%, and the description does not compensate.

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 restates the tool name ('Xero connector operation list_repeating_invoices') but does not explicitly state its purpose: listing repeating invoices. The name is clear, so it's minimally adequate, but the description adds no further clarification.

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 on when to use this tool versus other list tools like xero_list_invoices or how the 'arguments' parameter should be structured. Missing context for selection.

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