Node SSL Certificates

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

Annotations already carry readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds the '(requires elevated)' permission note for upload/delete and implies list is read-only via 'view certs', which is useful beyond the annotations. No contradiction with annotations: mutable and destructive operations match destructiveHint=true.

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?

Compact single sentence using pipe-separated action enumeration. Purpose is front-loaded ('Manage node SSL certificates') followed immediately by the action breakdown. Every segment earns its place, and the structure is highly scannable for an agent parsing the definition.

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 a 6-parameter, 3-action tool with no output schema, there are notable gaps: no per-action parameter mapping, no explanation of what the 'restart' and 'force' booleans do in context of each action, and the return of 'list' (certs, fingerprints, expiry) is left to inference. The description covers the what but not the how-combined, leaving an agent to guess parameter interactions.

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 all six parameters (key, node, force, action, restart, certificates) are already documented. The description's action explanations mirror the enum already in the schema. It does not add field-level guidance such as which parameters each action requires (e.g., upload needs certificates+key, delete likely uses force or restart). Baseline 3 is appropriate since the schema does the heavy lifting.

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?

States the resource ('node SSL certificates') and enumerates three actions with concrete outcomes ('list: view', 'upload: upload custom cert', 'delete: remove custom cert'). The 'node SSL' qualifier distinguishes it from the ACME-cert sibling (proxmox_acme_cert), though it never names that alternative. The verb 'Manage' is soft, but the explicit action breakdown carries the meaning.

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?

No when/when-not guidance. It describes the three actions internally but offers no reason for choosing this tool over proxmox_acme_cert, proxmox_node_service, or other cert/node siblings. There are no exclusions, alternatives, or conditions that would tell an agent when this tool is the right one.

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