pve_node_acme_domains_set

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

Discloses dry-run by default, replace semantics (stale entries removed), medium impact (config only, no cert issued), and mentions smoke-confirm. No annotations provided, so description carries full burden; it covers key behavioral aspects well.

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?

Well-structured with clear first sentence, then workflow, then parameter details. Every sentence adds value, though slightly long. Minor improvements possible by trimming redundant phrasing.

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 workflow, parameter semantics, behavior, and even includes a smoke-confirm note. Has an output schema so return values not needed. Could mention prerequisites (e.g., account must exist), but overall complete for a mutation tool in an ACME workflow.

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 only 17%. Description explains the domains/plugin relationship (DNS-01 vs http-01) and confirm role, but does not detail node, account, or proximo_target. Partially compensates but leaves gaps.

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?

Description starts with 'MUTATION: set a node's ACME account + domains' and further explains its role as 'The what to issue half of an ACME cert', clearly distinguishing it from sibling ACME tools like pve_acme_account_create 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 when to use: 'pair with pve_acme_account_create + pve_acme_plugin_create, then issue with pve_acme_cert_order'. Also explains two challenge methods, replace semantics, and that confirm=True is needed to execute. No when-not-to-use stated but context is clear.

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