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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety is largely covered. The description adds one genuinely useful behavioural constraint (class-wide content only, never about individual children) and the id-based update mode, but says nothing about whether the entry becomes immediately visible to parents or triggers notifications.

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 short front-loaded sentences, no filler, and the create/update distinction appears before the content restriction. Slightly terse in places ('mit id'), but nothing is wasted.

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 an 11-parameter write tool with no output schema and no annotations beyond safety hints, the description is adequate but thin: it leaves class vs. class_id resolution, required vs. optional field combinations per kind, and the effect of the write on the parent-facing page unexplained.

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 82%, so the schema already explains id, kind, date and the rest; the description only echoes the id-means-update semantics. It gives no guidance on ambiguous fields such as class vs. class_id, which both exist with no stated precedence.

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 verb pair (anlegen/ändern) and the resource (Eintrag auf der Elternseite einer Klasse), with the create-vs-update switch spelled out via 'mit id'. It is clearly distinguishable from list_parent_items and delete_parent_item, though it never names them.

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 sentence 'Nur Inhalte für die ganze Klasse – nie etwas über einzelne Kinder' is a content policy, not usage guidance. There is no statement of when to prefer this over delete_parent_item/list_parent_items or of prerequisites (e.g. which class must exist first).

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