provider_create_user

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the mutation profile is covered. The description adds one genuinely useful behavioral fact beyond that — LDAP and provider org VIDB users are validated against the backing IDP before import — but says nothing about required permissions, failure behavior, or what happens on duplicate usernames.

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?

Front-loaded with the action in the first two words, and only three short sentences. The trailing 'POST /cloudapi/1.0.0/users' duplicates the annotation title and earns little, but overall it is tight.

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 mutation tool with no output schema, the description is adequate but thin: it never says what a successful call returns (presumably the created user object), whether scope is provider/org level, or how orgEntityRef and providerType interact. Annotations carry the safety profile, which limits the damage.

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% and the single top-level `body` parameter is richly documented, including password complexity rules and read-only fields. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: 'Create a new user', which cleanly identifies the operation. It does not distinguish itself from adjacent user-management siblings (provider_update_user, provider_modify_user_groups, provider_query_users), but the create semantics are unambiguous.

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?

Usage is only implied by the verb 'Create' — there is no statement of when to use this versus provider_update_user or provider_take_ownership, no prerequisites such as required admin rights, and no exclusions. The IDP-verification sentence hints at a precondition for LDAP/VIDB users but is framed as behavior, not guidance.

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