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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds valuable behavioral context: the returned fields, the scale direction (0 = bester Wert), and a strong privacy warning, without contradicting the 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 compact sentences with zero filler: the first front-loads what data is returned, the second adds the optional filter and critical privacy constraint. Every sentence earns its place.

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 no output schema, the description usefully describes the returned fields (Tag, Satzanfang, Skala, Text) and the privacy audience. It is nearly complete, though the unresolved class vs class_id parameter ambiguity leaves a small gap.

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 only 33%; class_id and student_id have no schema descriptions. The description adds only that student_id is optional and does not clarify the distinction between class and class_id or the meaning of student_id filtering, leaving key parameter semantics undocumented.

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 states a specific read operation (Reflexionen der Kinder einer Klasse) tied to the ‘Reflexion’ widget and enumerates the returned fields. It clearly distinguishes this from sibling list tools by its unique resource and privacy scope.

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?

It gives clear context for use: reflections of a class, optional student_id filtering, and an explicit privacy constraint (‘Nur für die Lehrkraft – nie der Klasse zeigen’). It does not name alternative tools or exclusion conditions, so it falls short of a 5.

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