Delete a SAML certificate

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

Beyond annotations (destructiveHint=true), description reveals that the deletion is permanent, SSO breaks immediately if the active certificate is removed, and advises checking other certificates first. Also flags that the path is unconfirmed, directing to get_saml_certificate for details.

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?

Three tight sentences with no filler. First states action and key requirement, second warns of SSO impact and suggests a mitigation, third acknowledges uncertainty and points to another resource. Every sentence earns its place.

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 tool with 3 required params and no output schema, the description covers: permanent nature, confirm requirement, critical side effect (SSO breakage), and cross-references to list and get tools. Could briefly mention what happens if the certificate doesn't exist, but effectively equips an agent to use the tool safely.

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 only 33% (only confirm described). The description mentions the confirm requirement and implies certificate_id via context, but doesn't explain saml_id or the exact relationship between parameters. The parameter names are fairly self-explanatory, but the description could add more clarity on what 'saml_id' refers to (the SAML configuration ID).

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?

Clearly states the tool permanently removes one SAML certificate with a specific verb ('remove') and resource ('SAML certificate'). Distinguishes from siblings like list, get, add by explicitly focusing on deletion and warning about SSO consequences.

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?

Provides explicit when-to-use (delete a certificate) and when-not (if it's actively validating SSO, check list tool first). Also specifies the confirm=true prerequisite, giving clear guidance on safe invocation.

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