delete_certificate_authority

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

The description adds 'WARNING: This is irreversible', which complements the destructiveHint=true annotation by specifying the permanence of the action. This is useful undisclosed context, though it could optionally mention effects on dependent certificates.

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 a single sentence with a direct statement and an explicit warning. Every word is purposeful, with no redundant content.

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 simple destructive operation with a well-documented schema and output schema, this description is sufficient. It lacks usage guidance for safety but compensates partially with the warning. The overall context is clear for an agent to invoke the tool.

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 input schema provides 100% description coverage for all three parameters, including the confirm gate and dry_run preview. The description adds no additional parameter semantics beyond what the schema already conveys, so baseline 3 is appropriate.

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 explicitly states 'Delete a Certificate Authority by ID', providing a specific verb and resource. This clearly differentiates from sibling delete tools such as delete_certificate and delete_crl by targeting the Certificate Authority specifically.

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 offers no guidance on when to use this tool versus alternatives, nor does it mention the confirm and dry_run safety parameters. The irreversibility warning is cautionary but does not direct the agent on usage or prerequisites.

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