xero_list_manual_journals

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

Annotations already mark this as read-only, idempotent, non-destructive, and open-world; the description adds that calls route through the governed project/account connector authority and that Spring enforces effect=read. It does not cover return shape, pagination, or auth failure behavior, but that is less critical given the annotations. No contradiction with the schema's const 'read' or annotations.

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 definition is compact: one routing sentence plus a seven-line argument list with no filler. The first line is somewhat redundant with the tool name, but the bulleted parameter explanations earn their place. The structure is easy to scan.

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?

The envelope parameters (effect, approval_ref, idempotency_key, routing) are explained sufficiently for this platform's read-only connector pattern, and an output schema exists so return values need not be described. Missing are the domain semantics of manual journals and any guidance on what `arguments` may contain, which an agent needs to call the Xero operation correctly. For a simple list connector, it is minimally adequate but not rich.

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?

With 0% schema description coverage, every parameter gets some semantic gloss (e.g., project_id as 'Authenticated Project UUID'), which is helpful beyond the bare title. However, `arguments` is only described as a 'JSON string of arguments for the connector operation' without any detail on valid keys or behavior, and several glosses use platform jargon. The description partially compensates for the schema gap but leaves the most important payload parameter underspecified.

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 opens by restating the tool's identity as 'Xero connector operation list_manual_journals' rather than explaining that it retrieves manual journals from Xero. The tool name supplies the verb and resource, but the description adds no plain-language behavior or output expectation. It identifies the Xero connector family but does not differentiate from xero_list_invoices or other Xero list tools 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 sentence tells an agent when to invoke this tool versus xero_api_request, xero_list_invoices, or other Xero list operations. The routing/authority note constrains how calls happen, not which tool to pick. There is also no mention of prerequisites such as a connected Xero account or exclusion cases.

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