finance_xero_reporting_pack

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions routing through a domain-agent dispatcher with authentication scope, but does not disclose side effects, read/write nature, or what the action actually does beyond being a dispatcher.

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 reasonably concise with three sentences and two bullet-like arg descriptions. It front-loads the main action but includes implementation detail about routing that may not be essential. Overall efficient but could be more informative.

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?

The tool is part of a large family of finance_xero tools. The description lacks specifics about what the reporting pack produces, expected input formats for message or inputs, and what output to expect (despite having an output schema). It is insufficient for an agent to correctly invoke the tool.

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 input schema has 0% description coverage, so the description must add meaning. It explains 'message' as a free-text objective and 'inputs' as an optional JSON string of structured inputs, providing useful context beyond the schema's titles and types.

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 runs the 'xero_reporting_pack' action but does not specify what reporting pack entails. It uses vague terms like 'free-text objective' without clarifying the tool's specific function. Among many sibling xero reporting tools (e.g., xero_balance_sheet_report), this tool's purpose is unclear.

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 individual xero report tools. There is no mention of prerequisites, appropriate contexts, or when not to use it.

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