pve_acme_plugin_update

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

With no annotations provided, the description carries the full burden. It discloses the mutation nature, dry-run behavior, confirm flag, and a specific risk (invalid credentials breaking renewal). This is good but could mention response behavior or side effects.

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?

Two concise sentences, front-loaded with 'MUTATION'. Every sentence adds value without redundancy. Highly efficient.

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?

Despite having an output schema, the description does not mention return values. It lacks details on what parameters do and the scope of updates. For a tool with 7 parameters and 1 required, the description is insufficiently comprehensive.

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 14% (only one parameter has a description). The tool description only adds minimal context for confirm (dry-run/execute) but does not explain other parameters like data, digest, disable, dns_api. It fails to compensate for the low schema coverage.

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 'update an ACME DNS challenge plugin', using a specific verb and resource. It indicates this is a mutation operation, which distinguishes it from sibling tools like pve_acme_plugin_create and pve_acme_plugin_delete, though it does not explicitly state when to use this over alternatives.

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 mentions dry-run default and the confirm=True flag for execution, plus a MEDIUM risk warning about invalid credentials breaking renewal. However, it lacks explicit guidance on when not to use this tool or references to alternatives.

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