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

Annotations already carry readOnlyHint=true and destructiveHint=false, so the read-only profile is covered. The description adds that it returns the current state for card rendering, but it does not describe response fields, error behavior, or auth requirements; for a read-only helper that is adequate but not rich.

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 text is compact: the scope and action are front-loaded, and the purpose clause is kept short. The bilingual duplication is the only repetition, and it serves agents that may rely on English rather than German.

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 single-parameter, read-only endpoint, the description covers what it does, when to use it, and why. It does not enumerate exact return fields, but the 'end state and countdown' clause hints at the output shape, and no output schema is provided.

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?

The schema supplies a single required approvalId (UUID), and the description links that ID to the object whose state is read ('einer Freigabe'). It does not explain the UUID format or additional constraints, but with one self-describing parameter that omission is low-impact.

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 exact action ('liest den aktuellen Zustand einer Freigabe' / 'reads the current state of an approval') and the resource ('Freigabe' / 'approval'), and immediately confines the tool to the interactive approval card. This clearly distinguishes it from siblings like approval_list or approval_decide.

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 'Nur fuer die interaktive Freigabe-Karte' clause is a clear when/where restriction, and the mention of rendering an old card's end state and countdown gives a concrete trigger. It does not explicitly name alternative tools, but the intended context is unambiguous.

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