cipp_create_group

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

The description adds context beyond annotations (e.g., high-impact, security/mail use cases, reversibility). However, it contradicts the idempotentHint=true annotation, as creating a group is inherently non-idempotent (duplicate groups may be created). This reduces transparency.

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 brief (two sentences plus a warning), front-loaded with the caution icon, and every sentence conveys essential information without 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?

No output schema is provided, and the description does not explain the return value (e.g., group ID, confirmation). The idempotency contradiction remains unresolved. Overall, it is adequate for a simple creation tool but lacks full context.

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 baseline is 3. The description ties the tool's use cases (security, mail) to parameters like securityEnabled and mailEnabled, but does not elaborate on parameter semantics beyond what the schema provides.

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 clearly states the tool creates a new group in the tenant, with specific uses (security policy assignments, mail distribution), distinguishing it from sibling tools like cipp_list_groups (listing) and cipp_create_user (user creation).

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?

The description advises confirming with the user before invoking and notes reversibility, but does not specify when not to use it (e.g., if an equivalent group already exists) or explicitly compare to alternative creation methods among siblings.

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