xero_balance_sheet_report

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

No annotations exist, and the description does not disclose whether this is a read-only operation, what data it returns, potential side effects, or any error conditions. Behavioral information is completely absent.

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 inefficient: it repeats the name and routing details without delivering meaningful content. It is under-specified rather than concise, wasting space on trivial details while omitting essential information.

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 is a report with many siblings and no annotations, the description is completely inadequate. It lacks purpose, usage guidance, parameter details, and behavioral context. The presence of an output schema does not compensate for the missing high-level information.

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 sole parameter 'arguments' has no schema description (0% coverage). The description only states it is a JSON string of arguments, adding no information about valid fields, structure, or required values. The description fails to compensate for the schema gap.

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 merely restates the tool name as 'balance_sheet_report' and identifies it as a connector operation, but does not explain that it retrieves a balance sheet report for an organization. It relies on the name to imply purpose and fails to differentiate from sibling Xero report tools.

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 alternatives like xero_profit_loss_report or xero_cash_flow_report. The description lacks context about scenarios or prerequisites.

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