xero_list_associations

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

No annotations provided. Description mentions routing and scope (JWT, tenant, company) but does not disclose whether the operation is read-only, requires specific permissions, or has side effects.

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?

Description is short but includes unnecessary routing implementation details. It is concise yet uninformative.

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?

Crucial information about what is being listed is missing. Despite having an output schema, the description does not hint at the return structure or data content.

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?

Only parameter is 'arguments' described as 'JSON string of arguments for the connector operation.' Schema coverage is 0%, and the description adds little detail about expected keys or 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?

Description restates the tool name 'list_associations' without specifying what kind of associations (e.g., invoices, contacts, projects). The generic phrase 'connector operation' lacks domain-specific purpose.

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 like xero_list_invoices or xero_list_contacts. No context on prerequisites or typical use cases.

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