xero_list_payroll_au_timesheets

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

With no annotations, the description should disclose behavior, but it only mentions routing through `/api/tools/invoke`. It does not state that the tool is read-only, what data it returns, or any side effects. The JWT/tenant/company scope is generic boilerplate.

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 but poorly structured, mixing a technical routing note with a terse parameter line. It is underspecified rather than concise, missing essential information.

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 provides no information about return values or behavior. It is incomplete for a tool with one parameter and no parameter descriptions, offering virtually no actionable context.

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 sole parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which merely repeats the schema type. With 0% schema description coverage, the description should explain what keys are expected, but it adds no semantic value.

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 merely states the tool name and routing details, without explicitly stating that it lists Xero payroll AU timesheets. It adds no value beyond the name and fails to distinguish from siblings like xero_list_payroll_au_employees.

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 is provided on when to use this tool versus alternatives such as xero_approve_payroll_au_timesheet or xero_create_payroll_au_timesheet. The description offers no context for usage.

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