eda_herunterladen

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

Goes well beyond the annotations: the file is written read-only under its portal name, is hashed, and is never modified, with the concrete output folder resolution rule (MAHNANTRAG_AUSGABE, else ~/Documents/Mahnantraege). It even explains why destructiveHint is set, so the apparent tension with 'nie verändert' is resolved rather than left as a contradiction.

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?

Five short, front-loaded statements ordered as purpose, when to call, when blocked, side effects, output location. No filler, and the parenthetical annotation note is compact and informative.

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?

There is no output schema, and the description compensates by stating the target folder, the read-only storage, and hashing. Combined with the guard conditions, an agent has everything needed to invoke it safely despite the minimal one-parameter schema.

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 must carry the meaning. It does define the real condition behind the single boolean parameter (the human must have seen the data overview and explicitly approved it), though without describing the parameter itself or what happens when it is false.

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?

Specific verb plus resource: 'EDA-Datei aus der offenen Portal-Sitzung herunterladen'. The scope qualifier '(nur Versandart EDA-Download)' distinguishes it from sibling write-flow tools such as portal_ausfuellen and portal_status.

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?

Explicit preconditions ('Nur aufrufen, wenn der Mensch die Datenübersicht gesehen und ausdrücklich freigegeben hat') and explicit blocking conditions ('Gesperrt, wenn das Portal Fehler meldet (FehlerDa) oder nicht freigegebene Warnungen offen sind'). The agent knows both when to call and when not to.

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