cipp_disable_user

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

The description adds value beyond annotations: it notes reversibility ('Reversible by re-enabling the account') and warns 'HIGH-IMPACT,' which is not captured in the destructiveHint or other annotations.

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?

Two sentences, front-loaded with the warning. No unnecessary words. Efficient structure.

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?

The tool has 2 required parameters, no output schema, and simple functionality. The description covers the core action, reversibility, and a usage caveat, which is complete for this 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 description coverage is 100%, so baseline 3. The description does not add extra meaning to the parameters beyond what the schema provides. The schema itself includes clear descriptions for userId and tenantFilter.

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 action: 'Disables a user account, blocking sign-in.' The verb 'disable' and resource 'user account' are specific. It distinguishes from sibling tools like cipp_list_users and cipp_offboard_user.

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 'Confirm with the user before invoking,' which provides a clear usage guideline. However, it does not explicitly mention when not to use this tool or compare to alternatives like cipp_offboard_user for permanent removal.

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