xero_executive_summary_report

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

No annotations provided. The description mentions routing under JWT/tenant/company scope but does not disclose behavioral traits such as read-only, destructive, or performance characteristics. With no annotations, the description carries the full burden and is insufficient.

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 concise but lacks structure and detail. It is not front-loaded with key information, and while brief, it fails to provide necessary context.

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 complexity of an executive summary report and the presence of an output schema, the description should explain what the tool returns or its business context. It is incomplete for effective selection and invocation.

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%. The only parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which adds minimal value beyond the schema. It does not explain the expected structure, required fields, or possible values.

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 connector operation for executive_summary_report but does not explain what an executive summary report is or what data it returns. It fails to distinguish from sibling 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 on when to use this tool instead of other report tools. No mention of prerequisites or alternatives.

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