xero_list_tax_rates

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

With no annotations, the description must cover behavioral traits. It mentions routing through JWT/tenant/company scope, adding some auth context. But it does not disclose whether the operation is read-only, pagination behavior, or limit implications. The lack of annotations combined with sparse description leaves significant gaps.

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 lines) and front-loaded with the tool name. However, the second section about routing is implementation detail that may distract from the core purpose. It is not overly long, but space is used inefficiently given the lack of critical information.

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 indicate what the tool returns or how to interpret results. The single parameter is poorly explained. With one param and no annotations, the description should provide far more context to make the tool usable.

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 coverage is 0%, so the description must explain the sole parameter 'arguments'. It only says 'JSON string of arguments for the connector operation', which is generic and provides no specifics on expected structure, required fields, or defaults. The agent gains no understanding of how to construct valid input.

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 clearly states the tool lists tax rates in Xero via the connector operation. It identifies the specific resource (tax_rates) and verb (list), distinguishing it from sibling tools like xero_list_invoices. However, it lacks specifics on what tax rates are included (e.g., all, active, etc.).

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. It does not describe context, prerequisites, or exclusion criteria. The agent receives no help in deciding between this and similar tools like quickbooks_list_tax_rates.

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