xero_list_items

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

The description mentions routing and scoping (JWT, tenant, company) but does not disclose behavioral traits beyond that. With no annotations, the description should clarify that this is a read-only operation, but it does not explicitly state that. The routing info is generic and applies to all tools.

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 (three sentences) and front-loaded with the operation name. However, it sacrifices informativeness for brevity. It is not overly wordy, but it could be more concise while still adding value.

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 single generic parameter and the existence of an output schema, the description should provide context about what items are and what the response contains. It lacks this context, making it incomplete for effective agent use.

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 only parameter 'arguments' is described as a JSON string of arguments for the connector operation, which essentially repeats the schema. With 0% schema description coverage, the description should specify what keys or values are expected within that JSON string, but it fails to do so.

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 repeats the operation name 'list_items' without explaining what 'items' are in the Xero context (e.g., products/services). It does not distinguish from sibling tools like xero_list_invoices or xero_list_contacts, leaving the resource type ambiguous.

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, nor are there any exclusions or prerequisites. The description does not help the agent choose between this and other listing tools.

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