xero_get_payroll_au_timesheet

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

No annotations provided, so description must disclose behavior. It only mentions routing details (JWT, tenant, scope) but no information on read-only nature, side effects, or output format. Output schema exists but is not described.

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 includes generic routing details that are likely common to all connector tools, adding no value. It does not front-load the key purpose, and the space could be used for explaining parameters or usage.

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?

Given the tool's purpose (retrieving a specific payroll AU timesheet), the description is severely incomplete. No explanation of what a timesheet is, how to identify one, or what the response contains. With 0% schema coverage and no annotations, the description provides virtually no useful 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 only parameter 'arguments' is a JSON string with zero schema description coverage. No explanation of expected keys (e.g., TimesheetID) or default values, making it impossible for an agent to know how to construct the argument.

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 only repeats the tool's name and operation path ('Xero connector operation get_payroll_au_timesheet') without specifying that it retrieves a specific timesheet. The verb 'get' is clear from the name, but the description fails to confirm the action or resource.

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 siblings like xero_list_payroll_au_timesheets or xero_approve_payroll_au_timesheet. No context for prerequisites or when not to use.

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