xero_list_employees_accounting

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

No annotations are present, and the description only notes generic routing (JWT, tenant, company scope). It fails to disclose whether the operation is read-only, destructive, or any other behavioral traits such as rate limits or authentication requirements.

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 brief (three sentences) but front-loads a redundant restatement of the name. The second sentence on routing is arguably unnecessary for tool selection. It could be more concise by directly stating the tool's function.

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, the description does not mention that the tool returns employee data. For a list operation, this omission leaves the agent unsure of the result. The description also lacks any mention of filtering, pagination, or other common list semantics.

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,' which clarifies its format. However, the description does not explain what keys or values are expected within that JSON string. With schema coverage at 0%, this adds minimal value beyond the raw schema.

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 repeats the tool name ('Xero connector operation list_employees_accounting') without stating that it retrieves a list of employees. The purpose must be inferred from the name alone, and the added routing detail does not clarify functionality.

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 sibling tools like xero_list_contacts or xero_list_invoices. The description does not distinguish its use case or mention any prerequisites or context for invocation.

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