pve_acme_account_delete

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

With no annotations, the description carries the full burden. It clearly marks the action as MUTATION and IRREVERSIBLE, explains the dry-run default behavior, and highlights high risk. This is valuable additional context beyond what annotations would provide.

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 extremely concise (two sentences) and front-loaded with the most critical information: mutation, irreversibility, dry-run behavior, and risk. 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?

Given the tool's high risk and the fact that it has an output schema (which doesn't need description), the description covers purpose, usage, and risk adequately. Could mention prerequisites (e.g., account must exist) but overall complete for an agent decision.

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 low (33%), but the description adds significant meaning for the 'confirm' parameter by explaining the dry-run pattern. It effectively compensates for the lack of schema descriptions on other parameters.

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 states the action explicitly: 'deactivate and delete an ACME account from the CA.' It uses a specific verb and resource, and distinguishes from siblings like pve_acme_account_create and pve_acme_account_update.

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?

It provides clear guidance: 'Dry-run by default. confirm=True to execute.' It also warns about high risk and TLS lockout, which helps the agent decide when to use this tool. No explicit when-not but risk context implies careful consideration.

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