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 real value by disclosing completeness behavior — results are included only 'soweit die Quelle sie liefert' and nichtöffentliche Punkte are excluded. That tells the agent the payload may be partial, which is exactly the kind of trait annotations cannot express.

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?

Three short clauses, front-loaded with the resource and its contents, then the exclusion caveat. No filler, though the phrasing is a noun phrase rather than a directive sentence.

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 must describe returns, which it does adequately, but for a tool requiring two mandatory arguments at 0% schema coverage the definition leaves the caller without any parameter context. Return-shape coverage is good; input coverage is absent.

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 0% and both required parameters (kommune, id) are completely undocumented in schema and description. The description never mentions that a municipality and a session identifier are needed or what format they take, so it fails to compensate for the coverage gap, though the singular 'Sitzung' faintly implies an id lookup.

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 resource (a single Sitzung) and enumerates its payload: Tagesordnungspunkte, zugehörige Vorlagen, and Ergebnisse. That distinguishes it from siblings like sitzungen (list) and vorlage/drucksache (individual documents), though the retrieval verb is only implied.

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?

No statement of when to use this versus sitzungen or vorlage, and no prerequisites are given. The only usage-adjacent information is the exclusion of non-public agenda items, which is a scope constraint rather than guidance.

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