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

Annotations already declare readOnlyHint=true and destructiveHint=false, which correctly characterizes this as a non-destructive scheduling operation. The description adds the useful detail that the call returns a job ID rather than the export artifact itself, which helps manage agent expectations. It does not disclose asynchronous behavior in more depth (e.g., that results may be delivered later or that jobs can fail after scheduling), but that is partly covered by the sibling status tool.

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 compact: one German sentence and one English translation, with the primary purpose and return value front-loaded. Each clause earns its place by conveying the schedule semantics and the job-ID mechanism. The minor redundancy between the two languages is acceptable for bilingual coverage and does not materially bloat the entry.

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?

For an 8-parameter tool with no output schema and 0% schema description coverage, the description provides the essential scheduling semantics but not enough detail on optional parameters, delivery behavior, or how to correlate the returned job ID with archive_export_status. The presence of the close sibling archive_export_status mitigates the gap, but a fully complete definition would explicitly mention polling and explain the optional filter/notification fields.

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%, so the description should compensate, but it only clarifies 'format' indirectly by listing formats in prose and establishes that 'since'/'until' define the export date range. It leaves 'target', 'reasoning', 'notifyEmail', 'senderProfileFilter', and 'mandantennummerFilter' unexplained; an agent must guess their semantics from names alone. The format enum provides self-documenting options, which keeps this at a baseline 3, but the description does not compensate strongly enough for the coverage gap.

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 ('plant ein' / 'schedules'), names the resource ('Archiv-Export'), and enumerates the supported formats (GoBD-CSV, DATEV, PDF-Bundle, Mandanten-Allokation). The distinction that it returns a job ID for status polling helps clarify it from a potential immediate-export tool, but it does not explicitly differentiate it from archive_export_status, which is the obvious sibling.

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 description states a clear trigger: schedule an export for a date range and receive a job ID, and the sibling list contains archive_export_status, implying that one would call this tool first and then poll with the returned ID. However, it never explicitly says 'use archive_export_status to check progress' or lists conditions under which another archive tool would be preferred, so the cross-tool routing is only implied, not stated.

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