xero_list_manual_journals

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

No annotations are provided, so the description carries full burden for behavioral traits. It mentions routing and auth scope, but fails to disclose whether this is a non-destructive read operation, pagination behavior, rate limits, or any side effects. Minimal transparency.

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 relatively concise but includes potentially unnecessary routing details (e.g., path under JWT). It is front-loaded with the operation name but could be more structured. No wasted words, but lacks depth.

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 presence of an output schema, the description should still explain input semantics and behavioral context. It fails to describe what 'list' means (e.g., full list or paginated), expected arguments, or return format. Incomplete for an effective agent invocation.

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%, so the description must compensate. It only describes the 'arguments' parameter as a 'JSON string of arguments' with no further detail. The agent cannot infer what fields are valid (e.g., dates, status filters). This adds no meaningful guidance beyond the schema itself.

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 the tool lists manual journals in Xero, with specific verb and resource. However, it does not differentiate from sibling tools like xero_list_invoices or xero_list_contacts, leaving ambiguity in purpose beyond the name.

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 (e.g., xero_get_manual_journal for a single journal). No context about prerequisites, filters, or scenarios. The agent receives no help in deciding to invoke this tool.

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