create_user

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true. The description adds important security behavior beyond annotations: no password/secrets can be supplied, and the user must set secrets personally. It does not state required auth/role, but it adds substantive context.

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 front-loaded and compact, providing the endpoint and key constraints early. There is minor redundancy in repeating 'Create a new user' and a long required-attributes sentence, but it remains readable.

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 create mutation with a rich schema and annotations, it covers the important password/secret restriction. However, the required-attribute prose is misaligned with the schema by omitting locale and adding admin/accessAllResources, so an agent relying on the description could form an invalid request body.

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%, so the baseline is 3, but the description's required-attribute list conflicts with the schema. It says admin and accessAllResources are required although they are absent from the schema, says roles is required although schema marks it optional, and omits the required locale field, making the prose misleading.

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 uses the explicit verb 'Create' with the resource 'user' and even includes the endpoint POST /v1/users. It clearly distinguishes this tool from sibling operations like retrieve_user, update_user, and delete_user.

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?

It implies use when provisioning a new user and gives a negative constraint: you cannot specify password/secrets. However, it does not explicitly compare with update_user or state prerequisites such as admin permissions, so guidance is only partial.

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