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 two useful behavioral constraints beyond the annotations: only current committees are returned, and member lists are excluded. It does not describe the shape of the returned records or any ordering/paging behavior, so the added value is real but limited.

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?

A single well-formed sentence with the resource and scope front-loaded and the parenthetical examples doing useful disambiguation. Nothing is redundant, though the terseness leaves gaps that a slightly longer sentence could have closed cheaply.

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 one-parameter read tool with no output schema, the definition is minimally sufficient: it says what is listed and what is excluded. It is incomplete on the identifier format for 'kommune' and on the fields an agent can expect per Gremium, both of which matter for chaining into sitzung or vorlage calls.

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 'kommune' is undocumented in the schema. The description only implies it identifies the Körperschaft; it never says whether it is a name, an official municipality key, or an internal ID, nor what happens on an unknown value. With one parameter and no schema help, the description should have compensated and did not.

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 the resource (Gremien) with concrete examples of what it covers (Rat, Ausschüsse, Bezirksvertretungen, Fraktionen) and a scope qualifier (aktuelle, einer Körperschaft). The retrieval verb is only implied by 'Die aktuellen Gremien', and there is no explicit reference to a sibling, but no sibling covers committees so the intent is still unambiguous.

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?

There is no statement of when to use this tool versus alternatives such as kommunen (to resolve the Körperschaft) or sitzung/vorlage (for members and agenda items). The only guidance is the negative 'ohne Mitglieder', which tells the agent what it will not get but not where to go instead.

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