export_hmrc_csv

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

No annotations are provided, so the description must carry the full transparency burden. It clarifies that the output is a CSV and mentions categorization/summary, but it does not disclose whether the operation is read-only, how the file is delivered (e.g., direct download or URL), or any side effects or prerequisites.

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 a single concise sentence that front-loads the primary action ('Export transactions') and includes key qualifiers. There is no redundancy or filler, making it highly efficient.

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 description lacks crucial operational details such as the delivery mechanism of the CSV (e.g., file content vs. download URL), authentication requirements, or whether the export is scoped to the authenticated user. While an output schema exists (per context signals), its absence in the provided data means the agent cannot rely on it. Still, for a straightforward export tool, the description is minimally adequate.

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 provides 100% parameter coverage, with descriptions for account_id, start_date, end_date, and filename. The tool description adds no additional parameter semantics beyond referencing the CSV export, so the baseline of 3 applies.

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 uses a specific verb ('Export') and resource ('transactions') with a clear output format ('HMRC-ready CSV'). It also mentions 'categorization and summary,' which adds specificity and distinguishes it from sibling tools like get_transactions/list_transactions that likely return JSON.

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?

The phrase 'HMRC-ready CSV' implies the tool is for generating tax-compliant exports, giving some context on when to use it. However, it does not explicitly compare against alternatives like get_transactions/list_transactions or state any exclusions, leaving the decision to the agent based on context.

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