delete_acme_certificate

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

The description adds 'WARNING: This is irreversible,' which goes beyond the destructiveHint annotation by explicitly stating the permanence of the action. It also specifies that the target is an 'ACME certificate entry,' clarifying what gets destroyed. This is useful context beyond the structured annotation.

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 two short sentences with the verb and resource front-loaded, followed by a concise, high-impact warning. No filler or redundant information.

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?

The description gives the essential purpose and irreversibility warning, but doesn't highlight the confirm parameter required for execution or the dry_run preview option. These are present in the schema, but for a destructive tool, the description could guide the agent to set confirm=true. The output schema and annotations fill some gaps, so completeness is adequate but not thorough.

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 description coverage is 100%, so the baseline is 3. The description adds minimal parameter semantics beyond the schema—only 'by ID' which corresponds to the certificate_id property already described in the schema. No additional meaning is provided for confirm, dry_run, or apply_immediately.

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 tool deletes an ACME certificate entry by ID, using a specific verb and resource. It distinguishes from general certificate deletion (delete_certificate) and other ACME operations like create, update, issue, or renew.

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 conveys the operation's scope: deleting an ACME certificate by ID. While it doesn't explicitly list alternatives or exclusions, the 'by ID' phrasing implies the prior use of search_acme_certificates, which is standard for such tools. No misleading or irrelevant guidance.

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