Add group member

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

Description states it is a write operation, idempotent (matching the idempotentHint annotation), and that it returns a fixed confirmation message. No contradictions with annotations.

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 sentences, each serving a clear purpose: first identifies as write operation, second explains action and idempotency, third provides usage guidance. No unnecessary words.

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?

Given no output schema, the description mentions the return behavior (fixed confirmation message). It covers behavioral traits, prerequisites, and idempotency, making it complete for the agent.

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% with descriptions for both parameters. The description adds extra context: IDs are UUIDs, examples given, and advises resolving IDs beforehand, which is beyond the schema.

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 clearly states 'Adds an existing user to an existing group by their IDs.' This is a specific verb+resource combination that distinguishes it from sibling tools like keycloak_group_member_remove.

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 provides when-to-use guidance: 'Resolve the IDs first with keycloak_group_list and a user listing tool; to undo, use keycloak_group_member_remove.' This clearly indicates prerequisite steps and an alternative tool for the inverse operation.

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