xero_cash_flow_report

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only mentions routing details (JWT, tenant, company scope) but does not indicate safety characteristics (read-only vs. destructive), rate limits, or side effects. The behavior after invocation is opaque.

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 very short but not concise in an informative way. It wastes the first sentence restating the name and platform path. The second sentence provides routing context that might be obvious. The parameter description is generic. It lacks structure and meaningful content.

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 tool's complexity (financial report with output schema) and many sibling report tools, the description is incomplete. It does not mention the output schema, return value format, or how it differs from similar reports. The agent would need to infer behavior from the tool name alone.

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 described as a 'JSON string of arguments for the connector operation.' This adds minimal meaning beyond the schema. With 0% schema description coverage, the description does not compensate by explaining what keys or values are expected. The agent has little insight into correct usage.

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 'cash_flow_report' operation, which names a specific Xero report. However, it does not explain what a cash flow report is or what it returns, and it fails to differentiate from sibling report tools like xero_balance_sheet_report or xero_profit_loss_report. The purpose is somewhat clear but lacks specificity.

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 is provided on when to use this tool versus other Xero report tools or alternatives. There is no mention of context, prerequisites, or conditions for invocation. The description is silent on usage scenarios.

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