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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful context about the metadata each entry carries (Version, Zweck, Frist, Empfänger, PDF-URL, Online-Ausfüllen-Link), but since an output schema exists, this return-content detail is partly redundant and adds limited behavioral depth.

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 German sentence front-loads the resource and enumerates forms well, but the closing English sentence ('Lists the official German employment agency forms for AVGS providers') restates the opening and does not earn its place. The parenthetical list of metadata fields is dense but relevant.

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 simple read-only listing tool with one optional enum parameter, an output schema and full annotation coverage, the description is essentially complete – the agent knows what categories exist and what each entry contains. Only sibling differentiation is missing.

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 100% and the single `formular` parameter is a fully documented enum, so the schema does the heavy lifting. The description mentions the form categories that correspond to the enum values but adds no filtering semantics beyond what the schema already provides – the baseline 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?

Names a specific resource (official Bundesagentur für Arbeit forms for AVGS measures under § 45 SGB III) and enumerates the exact forms returned (Teilnahmebezogener Bericht, Fehltage, AMDL, § 16k Bericht). The purpose is unambiguous, but it never distinguishes itself from the sibling tools (avgs_fristen, bdks_pruefen, glossar), so an agent must infer the routing itself.

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 what the tool contains but gives no when-to-use guidance, no mention of the optional `formular` filter's role in usage, and no exclusions or alternatives relative to the sibling tools. An agent has no textual signal for choosing this over glossar or avgs_fristen.

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