xero_list_statements

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

No annotations are provided. The description only mentions routing, JWT, tenant, company scope, but does not disclose behavioral traits such as read-only nature, rate limits, or side effects. The agent gets no insight beyond generic infrastructure details.

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 includes unnecessary technical routing details (e.g., 'Routes through /api/tools/invoke') that are more internal than useful for selection. Could be more concise by focusing on the tool's 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 0% schema description coverage and no output schema visible, the description fails to explain what the tool returns or what 'statements' are. It is incomplete for effective 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 a JSON string with no explanation of structure or expected keys. Schema coverage is 0%, and the description adds nothing about valid inputs, making it unusable for proper invocation.

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 is a 'list_statements' operation for Xero, but does not explicitly define what 'statements' are (e.g., bank statements) or distinguish it from other xero_list_* tools. It conveys the verb+resource vaguely.

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 like xero_list_accounts or other Xero list operations. No context on prerequisites or scenario suitability.

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