xero_list_accounts

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 scope (JWT, tenant, company) but fails to indicate that this is a read-only operation, any side effects, or what the tool actually does operationally (e.g., fetches a list of Xero accounts). The output schema exists but is not referenced.

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 moderately concise (4 sentences) but includes redundant information (e.g., repeating the tool name and platform identifier). It could be more efficient by removing repetition and front-loading the actual purpose.

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 simplicity of the tool (one parameter, likely a list operation), the description still lacks completeness. It does not explain return format, pagination, filtering, or how it differs from sibling list tools. The output schema is present but not utilized in the description.

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% for the single 'arguments' parameter. The description says it is a 'JSON string of arguments for the connector operation,' which adds minimal meaning beyond the schema's type. It does not specify what keys or values are expected within that JSON, leaving agents to guess.

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 simply restates the tool name ('Xero connector operation list_accounts') without explaining what 'accounts' refers to or what the operation does. It provides no verb-resource clarity beyond the name itself, making it tautological and insufficient for distinguishing from other list tools.

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?

The description offers no guidance on when to use this tool versus alternatives like xero_list_contacts or xero_list_invoices. There is no mention of prerequisites, context, or scenarios where this tool is appropriate.

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