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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'Rein lesend' largely repeats structured data. The description does add scoping context ('eigenen Bereiches') and the pre-change inspection purpose, but says nothing about pagination behavior or result limits beyond what the schema provides, so a 3 is appropriate against an annotation-covered baseline.

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?

Purpose is front-loaded and the three routing clauses are compact and useful. The trailing '| EN: member, participant, membership, team' block is keyword padding rather than operative instruction, which slightly dilutes an otherwise tight definition.

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 read-only listing tool whose safety profile is fully covered by annotations, the description supplies purpose, scoping, and sibling routing. Return-value detail lives in the schema's scope_id description, and there is no output schema to account for, so the only minor gap is explicit pagination guidance.

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 100%, and the schema itself carries the meaningful details (20 members per page default, can_manage_scope=1 requirement, and that only email + rights + sp_id are returned). The description adds no parameter-level information beyond the schema, so the baseline 3 is correct.

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?

States a specific verb and resource ('Mitglieder ... auflisten') plus a scope qualifier ('eigenen Bereiches'), so the agent knows exactly what is returned. It also names the sibling operations it is not (toggle_member_flag, remove_member), making it distinguishable without opening a schema.

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?

Gives an explicit when-to-use ('den Ist-Stand vor Aenderungen zu sehen') and routes three adjacent operations to their correct tools: rights changes to toggle_member_flag, removal to remove_member, invitations to create_invite_code. The alternatives and the selecting condition are spelled out.

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