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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by disclosing the shape of the payload, including the conditional branch (bei Anfragen die Antwort der Verwaltung, bzw. umgekehrt). It does not mention behavior on invalid ids or unknown Kommunen, but for a read-only lookup that is a minor gap.

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?

Two compact blocks: the return-contents inventory first, then the parameter glossary. Every clause carries information and nothing is padded. Minor cost is the long comma-chained field list, which is dense but appropriate for enumerating a rich payload.

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?

With only two required params, no output schema, and safety covered by annotations, the description supplies the two things an agent actually needs: what comes back and where the identifiers come from. Missing only edge-case behavior (invalid id, ambiguous Kürzel), which is tolerable for a simple read lookup.

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 0%, so the description must carry both parameters, and it does: `kommune` is defined as a Kürzel and `id` as the number taken from the Vorlagen-URL or from `vorlagen_suchen`. That is a real semantic gain over bare string fields, especially the provenance of the id. It stops short of giving the id's concrete format or pointing to the source of valid Kürzel values.

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 names the specific resource (a Vorlage) and enumerates exactly what is returned: Titel, Art, Datum, Gremium, Zusammenfassung, Dokument, Beratungsfolge, plus the Antwort der Verwaltung for Anfragen. This is materially more specific than a tautology. It never explicitly contrasts itself with the sibling `vorlagen_suchen`, though the reference to obtaining the id from that tool implies the detail-vs-search split rather than stating it.

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?

Usage is only implied: the note that the id comes 'aus der Vorlagen-URL bzw. aus `vorlagen_suchen`' tells an agent this is the detail-fetch following a search, which is a useful path hint. There is no explicit when-to-use/when-not statement and no guidance on prerequisites such as where a valid `kommune` Kürzel comes from (e.g. the `kommunen` sibling).

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