xero_create_association

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

With no annotations, the description must disclose behavioral traits. It only mentions routing and authentication scope (JWT, tenant, company). It does not disclose that this is a write operation, potential side effects, idempotency, or required permissions. The agent gets minimal insight into the tool's impact.

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 unnecessary implementation details about routing through /api/tools/invoke. It is front-loaded with the tool name but lacks clear purpose. While not verbose, it sacrifices meaningful content for brevity.

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 the tool's low complexity (one parameter, output schema exists), the description is severely incomplete. It fails to explain what an association is, when to create one, or what the arguments string should contain. The output schema may cover return values, but input semantics are entirely absent.

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 0% description coverage for the sole parameter 'arguments'. The description only says it's a 'JSON string of arguments for the connector operation', adding no structural details or value. The agent is left without knowing the expected keys or value formats, making correct invocation difficult.

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 merely restates the tool name as 'Xero connector operation create_association' without explaining what an 'association' is in the Xero context. It fails to differentiate from sibling tools like xero_create_contact or xero_create_invoice, leaving the agent confused about the specific resource being created.

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. There is no mention of prerequisites, scenarios, or exclusions. The agent receives no help in deciding to invoke this tool over any other xero_create_* tool.

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