pve_acme_cert_revoke

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

With no annotations, the description fully discloses the irreversible mutation, async behavior (returns UPID), dry-run default, and high importance warning. It adds context about the confirmation parameter and a smoke-confirm testing note.

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 front-loaded with key action and warnings. Every sentence adds value, but it is somewhat lengthy. The structure effectively conveys purpose, usage, and consequences.

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 output schema (not shown), description doesn't need return values. It covers core behavior, prerequisites, consequences, and alternatives. Node parameter could be clarified, but overall adequate for a 3-param 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 schema has 33% description coverage (only proximo_target described). The description adds meaning to the confirm parameter by explaining its role in execution. However, node parameter is not described beyond the schema's minimal info.

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 revokes the node's ACME TLS certificate at the CA. It uses a specific verb ('revoke') and resource, and distinguishes from sibling tools like pve_node_cert_delete and pve_acme_cert_order.

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?

Explicitly states dry-run by default and that confirm=True is needed to execute. Provides clear when-to-use and when-not-to-use guidance, including an alternative (pve_node_cert_delete) and consequence (only a new pve_acme_cert_order restores trust).

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