xero_list_payroll_au_employees

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions routing through /api/tools/invoke under JWT/tenant/company scope, which is generic. It does not state whether the operation is read-only or if it has side effects.

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 (3 sentences) and avoids fluff, but includes routing information (API endpoint, JWT, tenant) that is likely unnecessary for an AI agent selecting a tool. It could be slightly more focused on functionality.

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 tool that lists specific entities (Australian payroll employees), the description lacks details about output structure, filters, or limitations. The presence of an output schema is noted but not leveraged in the description.

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 single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation,' with no further details on expected keys or structure. Schema coverage is 0%, and the description does not compensate with examples or references.

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 repeats the tool name without elaborating on what 'payroll_au_employees' means. It does not explicitly state that the tool lists Australian payroll employees, relying on the name for clarity. Among similar Xero list tools, this offers no differentiation.

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 alternatives like xero_list_payroll_au_timesheets or xero_list_invoices. The description does not mention any prerequisites or contexts.

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