xero_get_payroll_au_timesheet

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description's main added value is the routing constraint: 'Routes only through the exact project/account governed connector authority.' It also clarifies that effect must be read. However, the approval_ref line mentioning 'resuming a write' is confusing in a read-only tool context, though not a direct contradiction because the description explicitly requires effect=read.

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 organized as a clear Args list, with the routing constraint and effect requirement stated up front. But much of the content is generic connector boilerplate that repeats across similar tools, and the approval_ref line adds noise rather than useful guidance for a read-only operation.

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?

Even though an output schema exists and annotations are present, the description omits the actual connector arguments and any example payload, which are essential for a passthrough tool with 0% schema description coverage. It also does not clarify whether this is a single-item fetch versus the list operation, nor what identifiers like TimesheetID might be expected inside the arguments JSON.

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 description adds some meaning beyond the bare schema by labeling project_id as an Authenticated Project UUID, connector_account_ref as a Project-bound connector account alias, and idempotency_key as a stable business-action identity. However, the critical 'arguments' parameter is only described as a 'JSON string of arguments for the connector operation,' with no detail about what the get_payroll_au_timesheet operation actually requires, so the agent still cannot confidently compose the payload.

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 is essentially a restatement of the tool name: 'Xero connector operation get_payroll_au_timesheet'. It never says in plain language that this retrieves a single AU payroll timesheet, and it does not distinguish the use case from sibling tools like 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 such as xero_list_payroll_au_timesheets, xero_approve_payroll_au_timesheet, or xero_revert_payroll_au_timesheet. The only usage-related statement is that it routes through the governed connector authority and that effect must be read, which is a constraint, not a selection guideline.

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