Contract Testing: Admin Create User

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

Annotations already indicate this is not read-only, not idempotent, and not destructive, so the agent knows it is a write operation. However, the description adds little beyond the tool name: it does not disclose whether the created user receives an invitation, whether it can be used with external IdP accounts, or how conflicts or duplicate emails are handled.

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 short and fronts the core purpose, but it spends several lines repeating parameter information already present in the input schema. The 'Toolset: Admin' line and the full parameter list add little marginal value.

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 mutating admin operation with no output schema and no behavioral disclaimers, the description is thin. An agent is left without knowing what the response will be, whether an email is sent, whether the user is active immediately, or what admin permissions are required.

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 the schema fully documents all six parameters. The description duplicates those same descriptions without adding additional meaning or clarifying relationships between fields such as externalIdpId and externalIdpUsername.

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 states a specific action ('Create a new user account') on a clear resource and scopes it as an admin operation. It is distinct from nearby siblings like admin_update_user or admin_invite_users, though it does not explicitly call out those distinctions.

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 given on when to use this tool versus alternatives like admin_invite_users, admin_create_system_account, or admin_set_user_roles. The 'Toolset: Admin' label is generic and does not help an agent choose among the many admin siblings.

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