Disable SCIM provisioning for the Organization

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

Beyond annotations (destructiveHint=true), the description adds that the action is permanent, requires explicit confirmation, details the deprovisioning behavior, and includes a technical note about the endpoint implementation (fetches config first, uses top-level DELETE). No contradictions with 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?

Four sentences, front-loaded with the key point ('PERMANENTLY disable SCIM'), and each sentence adds important information: confirm requirement, immediate effect, deprovisioning risk, and technical implementation detail. No wasted words.

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 description covers purpose, required parameter, behavioral consequences, and even a technical note for correctness. It is nearly complete for an agent to decide and invoke safely. The only minor gap is the lack of mention of the return value or confirmation response, but that is not critical given the destructive nature.

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 mentions 'Requires confirm=true', which reinforces the schema's 'const: true' description but adds no new syntax or format details. The parameter semantics are adequately covered but not enriched beyond the schema.

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 opens with 'PERMANENTLY disable SCIM', clearly stating the action (disable) and resource (SCIM provisioning for the Organization). It distinguishes itself from siblings like scaleway_iam_enable_scim and scaleway_iam_get_scim_config by its destructive nature and the confirm requirement.

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 explicitly requires 'confirm=true', warns that provisioning stops immediately, and highlights the critical deprovisioning risk: 'if the IdP was the mechanism offboarding relies on to remove departed Users, that stops working silently until re-enabled.' This provides strong context on when to use and the consequences, though it does not explicitly name alternatives.

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