Delete identity provider

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

Annotations already indicate destructiveHint=true, so the destructive nature is known. The description adds that confirmation is required, which is a behavioral trait beyond annotations. However, it does not disclose other potential impacts (e.g., cascading effects, irreversibility).

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 very concise—two sentences with no fluff. It is front-loaded with the core action. While it could include more detail, it earns its place by being minimal and to the point.

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?

Given the tool's destructive nature (destructiveHint=true), the description lacks important context such as what happens after deletion, whether it is reversible, or any side effects. No output schema exists, and parameters are not explained. The description is inadequate for complete understanding.

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?

The description does not explain the parameters. The schema has 2 parameters (alias, confirm) with 0% description coverage. The phrase 'Requires confirmation' hints at the confirm parameter but does not specify its value or the alias parameter's meaning. The agent would have to infer from the schema alone, which is insufficient.

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 (delete) and the resource (identity provider). The tool name and title also reinforce this, making it unambiguous. Among siblings like keycloak_idp_create and keycloak_idp_list, this tool is distinct.

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?

No guidance is provided on when to use this tool vs. alternatives. There is no mention of prerequisites, when deletion is appropriate, or when to use other tools like keycloak_idp_create. The description only states 'Requires confirmation,' which is more about usage than context.

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