pve_acme_plugin_create

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

No annotations provided, so description carries the burden. It discloses mutation nature and dry-run behavior, but misses authorization needs, side effects, or consequences of execution beyond creation.

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?

Description is short and to the point, with key info front-loaded. Could be improved with structured list or separate sentences for different aspects, but currently 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?

With 7 parameters (2 required) and low schema coverage, description only clarifies a few. Output schema exists, but overall context of creation flow, prerequisites, and error states is missing. Underpments for a complex mutation 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?

Schema description coverage is only 14% (only proximo_target documented). Description adds meaning for dns_api and mentions plugin_id/plugin_type implicitly, but leaves 'data', 'disable', and others unexplained. Partial compensation but insufficient.

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 it creates an ACME DNS challenge plugin, with 'MUTATION' prefix indicating a write operation. It distinguishes from siblings like pve_acme_plugin_delete and pve_acme_plugin_update by being a create tool, but does not explicitly compare.

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?

Describes dry-run default and confirm=True to execute, and provides example for dns_api. However, lacks guidance on when to use this over update/delete or other ACME tools, and no exclusions or preconditions.

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