pve_acme_cert_renew

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

Discloses mutation, dry-run default, async, CA-validated, fails safely (cannot lock out), reloads pveproxy on success, and force option. With no annotations, description carries full burden and covers all key behavioral traits.

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?

Dense but efficient; front-loads key info and includes alternatives. Could be slightly more structured but every sentence adds value.

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?

Covers mutation type, safety profile, async behavior with output (UPID), and alternatives. Output schema exists, but description explains return value context. Fully adequate for an agent.

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?

Adds significant meaning to all 4 parameters beyond the schema: explains node default, force condition, confirm as dry-run vs execute, and proximo_target for multi-target config. Schema coverage is 100%, but description enriches each parameter.

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?

Clearly states it renews the node's existing ACME TLS certificate and distinguishes from siblings by naming alternatives: pve_acme_cert_order for fresh certs and pve_node_cert_delete for self-signed revert.

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 explains dry-run default, async behavior with UPID return, and that confirm=True is needed to execute. Provides context on when to use alternatives and the force option.

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