xero_list_accounts

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

Annotations already communicate read-only, idempotent, non-destructive, and open-world behavior. The description adds useful routing and verification details: it must go through the project/account governed connector authority and Spring enforces effect=read. It does not address pagination, authentication prerequisites, or failure modes, and the approval_ref note about resuming a write feels out of place for a read-only operation.

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 compact and well-structured, with the purpose first and a clean Args block. The platform tool path is slightly redundant with the tool name, but every line otherwise earns its place.

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?

Annotations and the output schema cover safety and return shape, and all parameters receive some semantic explanation. However, the agent is still missing explicit selection guidance and concrete details about what belongs in the arguments JSON for Xero's list_accounts operation, so invocation is not fully self-contained.

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?

With 0% schema description coverage, the description carries the parameter-documentation burden and does so for all seven fields. It explains effect's required read value, the arguments JSON string role, project_id as authenticated UUID, and connector_account_ref as a project-bound alias. The main gaps are that the structure of the arguments JSON is not defined and some definitions are terse or confusing in a read context.

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 identifies this as the Xero connector's list_accounts operation and states that it routes through the governed connector authority, so an agent can tell this is the Xero account-listing tool. It does not explicitly describe what the list returns or contrast with sibling Xero list tools, but the operation name and platform path make the purpose reasonably clear.

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?

There is no statement of when to pick this tool over alternatives such as xero_api_request, xero_list_contacts, or list_connectors. The only guidance is the routing constraint and the required read effect, which are invocation conditions rather than selection guidance.

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