finance_xero_reporting_pack

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

The annotations already provide destructiveHint=true and idempotentHint=false, and the description does not contradict them. It adds useful context about routing through the domain-agent dispatcher under JWT, tenant, and company scope, but it does not disclose what side effects may occur or what the action changes. No annotation contradiction found.

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, front-loads the action name, and uses a clear Args section. The routing sentence is somewhat implementation-focused but still informative. Overall it is tight and readable without unnecessary bloat.

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 simple two-optional-parameter interface and the presence of an output schema, the description is minimally adequate for invocation. The main gap is that it never explains what xero_reporting_pack is or produces, which matters for selecting this tool among the many finance_xero_* and xero_* siblings. An agent could call it, but not confidently know why it is the right choice.

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?

Input schema coverage is 0%, so the description must compensate. It defines message as a free-text objective and inputs as an optional JSON string, which adds basic meaning beyond the schema. However, it does not explain what structured keys or values inputs should contain, how message relates to inputs, or provide examples. The compensation is partial at best.

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 identifies a specific action to run (finance domain agent action `xero_reporting_pack`), so there is a verb and resource. However, it never states what the reporting pack actually does, what reports it includes, or what outcome the agent should expect. This is more concrete than a pure tautology but still relies heavily on the tool name for meaning.

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?

There is no guidance about when to use this tool versus alternatives. The description simply says to run the action, without mentioning similar finance/xero tools such as finance_xero_org_overview, finance_xero_close_books, or the raw xero_* reporting tools. The agent must infer usage entirely from the name.

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