Create user

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

Discloses beyond annotations: indicates it's a write operation (non-read-only), not destructive, non-idempotent (consistent with idempotentHint=false), and adds that it doesn't set passwords or send emails. Annotations are minimal but description fully covers behavioral traits.

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 adding value. Front-loaded with main action. No redundancy. Perfectly sized for the information needed.

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 the tool's simplicity (4 params, no output schema), the description is fully complete. It covers creation, post-creation steps, idempotency, and references sibling tools. No gaps.

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%, so baseline is 3. The description repeats parameter defaults (enabled true, emailVerified false) but adds no new semantics beyond the schema. It mentions username uniqueness but that's already in schema. No additional param-specific context needed.

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 the tool creates a new realm user and returns a confirmation message. It distinguishes from siblings by noting it does not set a password (use keycloak_user_reset_password) and is not for updates (use keycloak_user_update).

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 states when to use (create user), what it does not do (set password, send email), provides alternative (keycloak_user_reset_password for credentials), and warns about non-idempotence causing conflicts.

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