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

Annotations are minimal (all false hints), so the description carries the full burden of disclosing side effects. It clearly states that the tool 'Legt einen Lead + Rückruf-Task in der Dispatch-Queue an' (creates a lead and callback task), indicating a write operation. It also discloses that processing is partly via an AI service in the USA, which is critical for consent/privacy. It additionally mentions the expected response time (<15 min). These are meaningful behavioral traits beyond what annotations provide, and there is no contradiction with 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 two well-structured paragraphs with no filler. The first sentence states the core purpose and differentiation; the second covers usage constraints and consent. Every sentence earns its place, and the critical consent requirement is front-loaded in the second paragraph. It is appropriately sized for the tool's complexity.

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 8 parameters (3 required), 100% schema coverage, and an existing output schema, the description provides everything an agent needs: purpose, usage criteria, side effects, consent requirement, and a mention of the dispatch queue. It does not need to describe return values because the output schema handles that. The description is complete for correct invocation.

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%, so the baseline is 3. The description adds minimal extra meaning: it summarizes the required fields (Name + Telefonnummer) and mentions optional fields (Schadenart/Anliegen/PLZ), and reinforces the consent condition for einwilligung_erteilt. However, the schema already describes each parameter and the consent condition in detail. The description does not introduce new parameter semantics beyond what the schema already provides, so it stays at the baseline.

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 opens with a clear verb+resource: 'Fordert einen kostenlosen Telefon-Rückruf durch einen Claimondo-Berater an' (requests a free phone callback). It explicitly names the sibling tool 'claimondo_melde_schaden' as the alternative funnel arm, and distinguishes when to use this tool: for customers who prefer to be called or when no slot fits/data is missing. It also states the concrete side effect (creating a lead + callback task), so an agent can unambiguously tell this tool apart from its siblings without opening schemas.

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 provides explicit when-to-use guidance: it contrasts with claimondo_melde_schaden and gives the conditions for choosing this tool ('für Kunden die lieber angerufen werden (oder wenn kein Slot passt / Daten fehlen)'). It also states the hard prerequisite: must only be invoked with einwilligung_erteilt=true after user consent. No ambiguity remains about when this tool is appropriate.

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