xero_list_payroll_au_superfunds

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions routing details (JWT, tenant, company scope) but does not address read-only nature, pagination, error handling, or idempotency. Minimal useful 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 is short but includes redundant routing details (e.g., platform tool path, invoke endpoint) that are likely not useful for an agent. It front-loads the tool name and operation type, but could be more concise and actionable.

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?

Despite having an output schema (per context signals), the description does not help the agent understand what the tool returns or how to construct the arguments parameter. Missing context for effective 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?

The schema has one parameter 'arguments' (string, default '{}') with 0% schema description coverage. The description merely restates 'JSON string of arguments for the connector operation' without explaining valid keys, filtering options, or expected format. Fails to compensate for lack of schema descriptions.

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 name 'xero_list_payroll_au_superfunds' clearly indicates a list operation for Xero Australian payroll super funds. The description confirms it's a connector operation, but does not explicitly differentiate it from other Xero list tools beyond the name.

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, required permissions, or prerequisites (e.g., Australian payroll setup). The description lacks any context for appropriate invocation.

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