Create user

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

Annotations indicate the tool is not read-only, not destructive, and not idempotent. The description adds no further behavioral context, such as requiring admin permissions, side effects on other entities, or error conditions. Given the annotations, the description fails to provide additional transparency.

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 extremely short (4 words), but it is under-specified rather than concise. It does not include essential information about parameters, realm context, or return behavior. While front-loaded, it fails to earn its place with meaningful content.

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 tool with 4 parameters, no output schema, and moderate complexity, the description is completely inadequate. It omits what the tool returns, error scenarios, auth requirements, and realm scope. An agent cannot reliably use this tool without external knowledge.

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?

The input schema has 0% description coverage for its 4 parameters. The description does not explain the meaning or defaults of 'email', 'enabled', 'emailVerified', or the required 'username'. The agent must infer semantics from names alone, which is insufficient for correct invocation.

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 'Create a realm user' clearly states the action and resource, but it is only slightly more specific than the tool name. It does not disambiguate from sibling tools like keycloak_user_update or indicate which realm (implicitly the current realm). A score of 3 reflects adequate but not excellent clarity.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., keycloak_user_update, keycloak_group_create). There is no mention of prerequisites, such as the realm needing to exist, or behavior like duplicate username handling. This leaves the agent without decision support.

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