xero_list_payroll_au_leave_periods

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

No annotations are provided, so the description must carry the full burden. It mentions routing and scope but does not disclose whether the tool is read-only, what data it accesses, or any side effects. The agent cannot infer safe usage from this description alone.

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) and front-loaded, but it wastes space on a routing detail that is unlikely to help the agent decide whether to use the tool. It could be more informative without adding length.

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 that there is an output schema (not shown) and the input is a single JSON string, the description fails to provide any context about return values, input fields, or typical usage. An agent has almost no actionable information to 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?

Schema description coverage is 0%. The description only says 'arguments: JSON string of arguments' without specifying what keys or values are expected inside that JSON. The agent has no way to know which parameters are supported or their format.

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 essentially restates the tool name as a 'connector operation' without explaining what a leave period is or how it differs from similar Xero payroll tools like leave types or timesheets. The name itself is somewhat clear (list payroll AU leave periods), but the description adds no additional purpose clarification.

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 such as xero_list_payroll_au_leave_types or xero_list_payroll_au_timesheets. There is no context about prerequisites, use cases, or when not to use it.

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