dokument verschieben

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description reinforces this by stating the Kennung and content are preserved and nothing is overwritten, and adds the human-confirmation workflow. It does not cover error cases or what happens on invalid bereich values.

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?

Four short sentences, front-loaded with the write warning 'SCHREIBT IN DIE AKTE', then the operation, then the invariant, then the confirmation gate. No 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?

For a mutation tool with no output schema and no destructive annotation, the description covers the safety-critical facts (writes to file, preserves content, requires confirmation). Only the bereich/unterordner parameter semantics remain thin.

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 only 40%, so the description must compensate. It adds meaning for bestaetigt (confirmation semantics) and implies fall/dokument are stable identifiers, but says nothing about the bereich enum or the optional unterordner, leaving gaps the schema also only partially covers.

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?

States a specific verb and resource: moving a file into a different Aktenbereich ('Datei in einen anderen Aktenbereich einsortieren'). This distinguishes it from datei_ablegen (filing new) and dokument_ordnen, though no sibling is named explicitly.

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?

Gives a concrete usage condition: only call with bestaetigt=true after asking the user. This is a clear gating rule for when the tool may be invoked. No alternative tools are named, so it falls short of a full 5.

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