xero_create_payroll_au_timesheet

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

Annotations already flag non-read-only, destructive, and idempotent behavior; the description adds genuine enforcement mechanics beyond those flags: 'Routes only through the exact project/account governed connector authority', 'effect: Claimed read or write effect; Spring verifies it', and 'approval_ref: Approved platform task UUID when resuming a write'. This explains the approval-gated write flow and idempotency contract. It does not explain why destructiveHint is true or what the write changes in Xero, but the governance context is substantive.

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?

Compact and well-organized: an identity line, one routing sentence, and a clean seven-row Args list with no padding. Each line earns its place, though the first line is slightly redundant by naming the operation twice (connector operation and platform tool).

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?

The output schema covers return behavior and annotations cover the safety profile, but an agent still cannot construct a correct call: the `arguments` payload content is unspecified, the relationship between approval_ref and fresh versus resumed writes is ambiguous, and there is no differentiation from the sibling approve/revert/list timesheet tools. The governed-routing context is strong, but the domain payload is the missing half.

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 must compensate, and it provides one-line semantics for all seven parameters — most genuinely informative ('Project-bound connector account alias', 'Stable business-action identity'). However, the central payload parameter `arguments` is defined circularly as 'JSON string of arguments for the connector operation' with no indication of what fields a create_payroll_au_timesheet payload needs (employee, period, timesheet lines), leaving the most important parameter the least explained.

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 opening line merely restates the tool name: 'Xero connector operation create_payroll_au_timesheet (platform tool xero.create_payroll_au_timesheet)'. It never states in domain terms what the operation does (e.g., record an employee's timesheet period and lines in Xero Payroll AU), so the agent must infer the action purely from the name.

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 alternatives. The sibling list contains xero_create_payroll_au_timesheet's family members — xero_list_payroll_au_timesheets, xero_get_payroll_au_timesheet, xero_approve_payroll_au_timesheet, and xero_revert_payroll_au_timesheet — yet none are mentioned or differentiated.

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