proxmox_certificate

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

No annotations are provided. The description discloses that upload and delete actions require elevated privileges, but it does not mention any other behavioral aspects such as side effects, return values, or the impact of parameters like 'force' and 'restart'. This leaves some behavioral ambiguity.

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 extremely concise: two sentences with no extraneous words. The first sentence establishes the overall purpose, and the second efficiently lists actions with brief descriptors. It is front-loaded and every word 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?

Given the lack of output schema and 6 parameters, the description covers the basic actions but lacks detail on return values, error handling, or the effect of optional parameters like 'force' and 'restart'. It provides minimal context beyond the action list, leaving gaps for a complete understanding.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; it merely summarizes the actions. The individual parameter purposes (node, certificates, key, force, restart) are not elaborated beyond what the schema already provides.

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 starts with 'Manage node SSL certificates,' clearly stating the verb and resource. It then enumerates three specific actions (list, upload, delete) with brief explanations. This differentiates it from sibling tools like proxmox_acme_cert, which handles ACME certificates.

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 implies usage for node SSL certificates via the title and action descriptions. It notes that upload and delete require elevated privileges, providing a usage condition. However, it does not explicitly state when not to use this tool or mention alternative tools for different certificate types.

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