xero_list_payroll_au_payitems

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

Since no annotations are present, the description must fully disclose behavioral traits. It fails to mention that this is a read-only operation, potential rate limits, required permissions, or any side effects. The routing information is technical but not behavioral.

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 includes redundant name repetition and technical routing info that may be unnecessary. It is adequately concise but not optimally structured for clarity.

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 simple list operation with many siblings, the description lacks completeness. It does not explain what payitems are, how to filter, or what the output schema provides, despite the existence of an output schema.

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 schema has only one parameter 'arguments' with 0% description coverage. The description adds that it is a JSON string of arguments but provides no details on the expected keys or structure, leaving the agent to guess or rely on external knowledge.

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 states it is a list operation for payroll AU payitems, which is clear about the verb and resource. However, it does not differentiate from sibling tools like xero_list_payroll_au_employees or xero_list_payroll_au_payruns, leaving ambiguity about the specific data returned.

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. The description only includes technical routing details, not practical usage context.

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