xero_list_payroll_au_superfunds

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds some context beyond annotations by stating that routing only occurs through the governed project/account authority and that effect must be read and verified by Spring. However, it does not disclose operation-specific behavior such as pagination, filtering, data scope, or rate limits, and the approval_ref note about resuming a write is slightly confusing for a read-only tool.

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 compact and the Args block is clearly structured. The first line duplicates the tool name and several parameter descriptions are generic, so not every sentence earns its place, but overall it is not bloated.

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 input side is under-specified for successful invocation. The description does not explain what the arguments JSON should contain for the Xero superfunds endpoint, what filters or options are available, or how the governance parameters relate to the actual connector call. The generic parameter glosses are not sufficient for an agent to confidently construct the operation payload.

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?

With 0% schema description coverage, the description partially compensates by glossing all 7 parameters, including clarifying that arguments is a JSON string and project_id is an authenticated project UUID. However, most definitions are generic boilerplate ('Stable business-action identity', 'Exact project correlation reference'), and the key arguments field gives no operation-specific payload structure or valid keys.

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 with "Xero connector operation `list_payroll_au_superfunds` (platform tool `xero.list_payroll_au_superfunds`)", which is essentially a restatement of the tool name and provides no functional statement such as "Lists superannuation funds for Australian payroll." The only real hint of purpose comes from the name itself, not from the description.

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 about when to use this tool versus alternatives. The sentence about routing through governed connector authority describes an invocation constraint, not a selection criterion, and there is no comparison to sibling tools like xero_list_payroll_au_payruns or xero_list_payroll_au_employees.

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