xero_cash_flow_report

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the routing constraint and the fact that Spring verifies the effect must be read. However, the approval_ref line ('when resuming a write') is confusing for a read-only operation, and the description does not explain what the cash flow report actually returns. No direct contradiction with annotations, so a 3 is appropriate.

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 compact and well-structured, with each argument on its own line and the routing constraint up front. The first line is redundant with the tool name, but the rest of the content earns its place without excessive verbosity.

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?

With 7 parameters and zero schema descriptions, the description must provide enough invocation guidance, but it does not specify what should be placed in `arguments` for the cash flow report, nor which Xero method it maps to. It also gives no context to distinguish it from the many sibling report tools. The output schema covers return values, but the input payload remains unexplained.

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 description coverage is 0%, so the one-line Args list is the only semantic guidance. It adds meaning to project_id, project_ref, connector_account_ref, idempotency_key, effect, and approval_ref. However, the critical `arguments` parameter remains opaque—'JSON string of arguments for the connector operation' does not say what the cash flow report operation expects—and project_ref is only vaguely defined as 'Exact project correlation reference'.

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 with 'Xero connector operation cash_flow_report (platform tool xero.cash_flow_report)', which simply restates the tool name and namespace. It never states a verb or outcome such as retrieving, generating, or listing a cash flow report. This is effectively a tautology and gives no way to distinguish this from other xero_*_report siblings.

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 like xero_profit_loss_report or xero_balance_sheet_report. The routing constraint ('Routes only through the exact project/account governed connector authority') and the effect requirement are constraints, not selection criteria. An agent receives no help deciding which report tool to invoke.

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