scim_create_group

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

No annotations are provided, so the description carries the full burden. It does disclose useful traits: rejected reserved names, a 404 for non-existent member IDs, and the optional/required split. It omits permission/auth requirements, name-collision behavior, and what the response returns, leaving meaningful gaps for a write operation.

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?

Four short sentences, front-loaded with the action and the required field, with each constraint earning its place. "Requires displayName" partly restates the schema's required array, which is the only mild redundancy.

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 4-parameter SCIM write with nested member objects and no output schema, the definition covers the constraints an agent needs to construct a valid call. It is missing auth/permission context and any note on the extension schema's optionality, but it is close to complete.

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 already documents members, schemas, displayName and the extension object. The description reinforces the required/optional split and the existing-user constraint on members but adds no syntax or format detail beyond the schema, so the baseline 3 is right.

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 precise verb+resource ("Create a group via SCIM") and the protocol qualifier helps separate it from the sibling create_group. It stops short of explicitly contrasting with that sibling, but the action and object 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?

Gives concrete preconditions: displayName is required, reserved permission group names are disallowed, members must reference existing users. However, it never states when to choose this over the sibling create_group or add_group_users, so routing guidance is only implied.

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