config_create_user

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the action 'Create a user,' but does not mention required permissions, side effects, mutability, or whether fields like password are mandatory. This is insufficient for a mutation tool.

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 minimal but under-specified. While 'Create a user.' is concise, it does not earn its place given the complexity of the operation; it omits critical information and is not appropriately sized for a 9-parameter create tool.

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?

Despite having an output schema, the description is completely inadequate. It does not explain what the response contains, dependent steps like user creation requiring security profiles, or any post-conditions. For a create operation with required dependencies, this is a severe gap.

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 0% and the description adds zero meaning beyond the parameter names. With 9 parameters including instance_id, routing_profile_id, and security_profile_ids, the description offers no explanation of relationships, defaults, or constraints, leaving the agent to infer everything from 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 'Create a user.' uses a specific verb and resource, clearly indicating the tool's function. It distinguishes from sibling tools that list, describe, or update users, though it doesn't explicitly mention the distinction.

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 like config_update_user_routing_profile or config_list_users. It also lacks prerequisites such as the need for existing routing/security profiles, making the usage context unclear.

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