proxmox_acme_account

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

No annotations are provided, so the description carries full burden. It only mentions elevated permissions for management actions, but omits other behavioral traits like idempotency, side effects of deletion, rate limits, or error conditions. This is minimal.

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 short (two sentences) and front-loaded with the core purpose. However, the action enum values are referenced but not fully mapped, and the schema's action description ('List all ACME accounts') is slightly inconsistent with the tool's description.

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?

For a tool with 5 parameters and no output schema, the description covers the basic action categories but lacks details on required fields for create/update, return format, error handling, and prerequisites beyond elevated permissions. It is adequate but not 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 100% with each parameter already described. The description adds the elevation requirement for certain actions, which is marginally helpful. It does not provide new parameter semantics beyond what the schema offers, so a baseline of 3 is appropriate.

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 'Manage ACME accounts' and distinguishes between query actions (list/get) and management actions (create/update/delete). It is clear about the tool's scope, but does not explicitly differentiate from sibling tools like proxmox_acme_cert or proxmox_acme_info.

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 provides basic usage guidance: query accounts with list/get and manage with create/update/delete (requires elevated). However, it does not explain when to choose this tool over alternatives, such as when to use proxmox_acme_info instead.

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