xero_list_payroll_au_employee_leave

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

With no annotations, the description must disclose behavioral traits but only mentions routing and argument format. It does not state whether the operation is read-only, what side effects occur, or any authentication or rate limiting details.

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 (two sentences) but includes redundant repetition of the tool name and platform reference. The routing information is likely unnecessary for agent understanding.

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?

For a payroll AU leave listing tool with only one parameter and an output schema, the description lacks critical information about what the output contains or what valid arguments are. It does not fully enable an agent to select and invoke the tool correctly.

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 a JSON string with 0% schema coverage. The description adds no semantic meaning beyond 'JSON string of arguments', failing to specify what keys or values are expected.

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 restates the tool name ('Xero connector operation `list_payroll_au_employee_leave`') without explaining what listing employee leave means or what it accomplishes. It does not distinguish from the sibling tool 'xero_list_payroll_au_employee_leave_balances'.

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 like 'xero_list_payroll_au_employee_leave_balances' or other payroll leave tools. The description lacks context on prerequisites or typical use cases.

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