accounting_export_zip

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

The description adds useful behavioral context by listing the archive contents and explaining SAGA chart-of-accounts overrides with fallback to stored settings. However, it does not disclose important export mechanics such as how the ZIP is returned, whether the operation is asynchronous, or any permission/rate-limit constraints, leaving meaningful gaps beyond the safety annotations.

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 front-loaded with the tool's purpose and then adds archive contents, filtering, and SAGA-specific override behavior. Every sentence contributes useful context without repetition or filler.

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 9 parameters, nested account structures, and no output schema, the description gives an adequate high-level picture: what is exported, which formats are targeted, and how SAGA overrides work. It omits some lower-level SAGA flags and delivery details, but the rich schema covers those parameter specifics.

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 coverage is already 100%, so the schema documents parameters including target, date filters, accounts, currencyAccounts, and SAGA-only flags. The description adds only limited parameter context: date filtering, the accounts override syntax, and SAGA-only behavior, but does not explain currencyAccounts or the other SAGA-specific flags.

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 a specific verb and resource: export accounting data as a ZIP archive for import into named accounting systems. It also scopes the archive contents, distinguishing it from narrower sibling exports such as invoices_export_zip or clients_export_saga_xml.

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?

It clearly establishes the intended use case: import into Saga, Winmentor, or Ciel, with optional date filtering. It does not explicitly compare against sibling export tools or state when not to use it, which keeps it below a 5.

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