xero_list_files

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

No annotations are provided, so the description must disclose behavioral traits. It mentions routing through JWT, tenant, and company scope, but does not state whether the operation is read-only, what side effects (if any) occur, pagination behavior, or error conditions. The lack of destructiveHint or readOnlyHint leaves safety unclarified.

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 not optimally front-loaded. The first sentence redundantly repeats the tool name. The routing information is likely irrelevant for the agent's selection and could be omitted. It earns its place but could be more direct.

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?

Despite having an output schema, the description fails to mention what the tool returns (e.g., list of file IDs, metadata). For a simple list operation, this omission leaves the agent uncertain about the response format. The description is incomplete for practical 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 single parameter 'arguments' has no schema description (0% coverage). The description says 'JSON string of arguments for the connector operation' – a tautology that adds no meaning. It does not explain what keys or values are expected, leaving the agent 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 states it's a 'list_files' operation, so the purpose is implied by the name. However, it does not specify what kind of files (e.g., attachments, documents) or how it differs from sibling tools like xero_list_folders. The description provides no concrete resource detail.

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 guidance on when to use this tool versus alternatives (e.g., xero_list_folders, xero_list_attachments). The description only mentions routing scope, not context or exclusions.

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