fossa_delete_saml_settings

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

Beyond the annotations (destructiveHint, readOnlyHint), the description explains the full consequences: users lose SAML login, domains go with the config, and the operation is irreversible because the API cannot read settings back. This adds significant value.

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 efficiently structured: action, prerequisites, consequences, and mitigation. Every sentence is information-dense and necessary, with no fluff or repetition.

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?

For a destructive, irreversible admin tool, the description covers prerequisites, side effects, irreversibility, pre-action steps, and parameter fallback. With an output schema present, no return-value detail is needed. This is complete.

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 0%, so the description compensates by explaining the fallback behavior of `organization_id` (falls back to FOSSA_ORG_ID). It also implies the parameter is optional, matching the schema. This adds meaning beyond the raw type.

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 a specific verb and resource: 'Remove the organization's SAML single sign-on configuration entirely.' This clearly distinguishes it from related tools like fossa_update_saml_settings and other delete operations.

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 clearly states the required environment flags (FOSSA_ALLOW_WRITES, FOSSA_ALLOW_ADMIN, FOSSA_ALLOW_DESTRUCTIVE) and provides cautionary guidance (copy settings, ensure admin access). It does not explicitly contrast with alternatives, but the context is clear.

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