xero_list_payroll_au_payruns

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the description only needs to add context beyond those. It does add useful routing and verification context: effect must be read and Spring verifies it, and calls route through governed project/account authority. However, the approval_ref note 'when resuming a write' is confusing for a read-only operation and introduces potential inconsistency even if it is not a direct annotation contradiction.

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 fairly compact and uses a clean argument list, with the routing constraint near the front. However, the first line is pure name repetition, and the Args section contains some boilerplate definitions that add little for this specific tool. It is structured and readable but not exceptionally tight.

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 and return-value documentation is not required, the description still lacks essential operational context. It does not explain what payroll AU payruns are, what inputs the connector operation expects, or how this differs from the many sibling Xero payroll listing tools. An agent is left to infer almost everything from the tool name.

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 bears full responsibility for explaining parameters. Most parameter descriptions are generic platform boilerplate (project_id, project_ref, idempotency_key, approval_ref), and the crucial `arguments` parameter is only described as a 'JSON string of arguments for the connector operation.' It does not specify what keys, filters, pagination options, or payroll-specific arguments the Xero list_payroll_au_payruns operation accepts.

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 operation name and platform tool name ('Xero connector operation `list_payroll_au_payruns`') without adding a meaningful verb/resource definition. It never explicitly says it lists Australian payroll pay runs, so an agent must rely on the name alone. It also does not distinguish this from sibling tools like xero_list_payroll_au_payitems or xero_list_payroll_au_timesheets.

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 on when to use this tool versus alternatives. The only contextual sentence, 'Routes only through the exact project/account governed connector authority,' is about authorization and routing, not about selecting this operation. No exclusions, prerequisites, or sibling-tool comparisons are provided.

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