xero_revert_payroll_au_timesheet

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool is destructive (reverting a timesheet likely modifies or deletes data) or if it requires specific permissions. The routing detail is not behavioral information.

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 contains three sentences, but the first two are purely routing boilerplate that does not aid tool understanding. The third sentence is a generic placeholder. The description is under-specified and wastes space on non-essential details.

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 complexity of a payroll revert operation and the lack of structured annotations or schema descriptions, the description is completely inadequate. It does not explain the tool's purpose, behavior, or parameters, leaving an AI agent without sufficient information for correct selection and invocation.

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%, and the description only states that the 'arguments' parameter is a JSON string, without specifying what fields or values are expected. This provides no meaningful guidance beyond the raw schema.

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 does not state what the tool does; it only repeats the name and provides routing information. It fails to specify that it reverts a payroll timesheet, which is essential for distinguishing it from siblings like xero_approve_payroll_au_timesheet.

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 (e.g., xero_create_payroll_au_timesheet, xero_approve_payroll_au_timesheet). The description omits any context about prerequisites or intended use cases.

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