fossa_delete_oidc_provider

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

The description adds significant behavioral context beyond the annotations: it explains the cascade effect (trust relationships are deleted with the provider), the consequence (workloads lose login ability), and the irreversibility ('Nothing here restores them'). This goes well beyond the destructiveHint annotation by detailing what gets destroyed and why caution is needed.

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 concise and each sentence earns its place. It starts with the core action, then lists prerequisites, then explains the cascade and provides a pre-delete step. The structure is logical and easy to scan, with no unnecessary filler.

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 destructive and cascading nature of this operation, the description covers the essentials: the action, prerequisites, consequences, and a recommendation for a pre-delete checklist. It does not explain the return value, but an output schema exists (as indicated), so that is not required. The description is complete enough for an agent to understand the full impact and necessary precautions.

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 schema provides only the parameter name and type (integer) with no description. The description implies that provider_id is the identifier of the OIDC provider to delete, and it mentions filtering on `provider_id` in the sibling list tool, giving some context. However, it does not explicitly state how to obtain the provider_id or that it is required, so it only partially compensates for the 0% schema coverage.

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 an OIDC provider and every trust relationship that points at it.' This is a specific verb+resource combination that also distinguishes itself from sibling tools like fossa_delete_oidc_trust_relationship, which only deletes a single relationship.

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 provides clear contextual usage guidance: it warns about the cascading deletion of trust relationships, lists required environment variables (FOSSA_ALLOW_WRITES, FOSSA_ALLOW_ADMIN, FOSSA_ALLOW_DESTRUCTIVE), and instructs the user to list trust relationships before deleting. It does not explicitly name an alternative tool for deleting just a trust relationship, but the cascade warning makes the scope clear.

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