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

The description adds substantial behavioral detail beyond the annotations: it writes membership, rights are only upgraded and never automatically downgraded, membership is permanent while the code itself expires, and all scope managers are notified. These details are consistent with readOnlyHint=false and destructiveHint=false.

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 reasonably front-loaded: it states purpose first, then write behavior, usage condition, validity, issuer alternative, and scope entry. The trailing English keyword list ('| EN: invitation, invite, voucher, code, bundle') is somewhat wasteful, but the overall structure remains efficient.

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 mutation tool with no output schema and clear annotations, the description covers purpose, usage context, key side effects, rights semantics, permanence, and validation requirement. Nothing essential for correct invocation appears missing.

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 coverage is 100% and the only parameter is fully documented in the schema, including an example and membership permanence. The description reinforces that the code must be valid and that the issuer manages it, but adds no new syntax or format meaning beyond the schema, so the baseline of 3 applies.

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 (einloesen) and resource (Einladungscode), and distinguishes the tool from related siblings by calling it the self-registration path without an administrator and by noting that the issuer manages codes via list_invite_codes. An agent can identify the tool's role without inspecting the 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?

Explicitly says to use it when you have received a code, and names list_invite_codes as the issuer-side management alternative. However, it does not state when not to use it or contrast it with other registration entry points beyond the brief 'Weg (a)' note.

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