xero_list_folders

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

No annotations provided, so the description bears full responsibility. It mentions routing and authentication but does not disclose whether the operation is read-only, destructive, or has side effects. No details on rate limits, pagination, or result content beyond the bare fact of listing.

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 three sentences, but the second sentence about routing is technical and not universally useful. While brief, it could be more focused on the actual functionality. It is not egregiously long, but it lacks structure and prioritization.

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 (as per context signals), the description does not explain what the tool returns. The input schema is minimal, and the description adds little context about how to use the arguments effectively. The tool is simple, but completeness is low due to missing output and usage details.

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 a JSON string with default '{}'. The description repeats the parameter name without explaining what arguments are expected (e.g., filters, pagination). Schema coverage is 0%, and the description adds minimal meaning beyond the parameter name.

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 clearly states this is a 'list_folders' operation for Xero, which is a specific verb+resource. It distinguishes from sibling tools like 'xero_list_files' or 'xero_list_accounts' by the resource type. However, it does not specify what kind of folders (e.g., document folders, accounting folders), leaving some ambiguity.

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 on when to use this tool versus alternatives. The description mentions routing and authentication scope but not use cases, prerequisites, or exclusions. Among many Xero list tools, there is no differentiation or context.

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