xero_bank_summary_report

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

No annotations exist, so the description carries full burden for behavioral disclosure. It mentions authentication scope (JWT, tenant, company) but fails to state whether the tool is read-only, what data it returns, or any side effects.

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 contains redundancy (repeating the tool name) and includes low-value technical routing info. While concise, it sacrifices clarity and completeness.

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?

For a financial report tool, the description is critically incomplete. It lacks output schema documentation, parameter guidance, and any description of the report's content or purpose. The output schema exists but is not leveraged.

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 single parameter 'arguments' has no description in the schema (0% coverage) and the tool description does not clarify what should be passed in the JSON string (e.g., date range, report parameters). This leaves the agent unable to construct correct input.

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 'Xero connector operation bank_summary_report' without explaining what the tool does (e.g., retrieves a bank summary report). It does not differentiate from sibling Xero report tools like xero_balance_sheet_report or xero_cash_flow_report.

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, nor any prerequisites or typical scenarios for invoking it.

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