pve_node_certificates

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

No annotations are provided, so the description carries the full burden. It correctly discloses the read-only nature and expected return fields. However, it does not mention required permissions, potential errors (e.g., node not found), or any side effects. For a simple list operation, this is adequate but not comprehensive.

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 two sentences, front-loaded with the core action, and every word adds value. It is concise without sacrificing clarity.

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 existence of an output schema, the description adequately returns field details. It covers the essential information for a list operation. However, it omits guidance on handling invalid or missing node input, and does not mention if the list is ordered or paginated. Still, it is mostly complete.

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 50%: only the 'proximo_target' parameter has a description. The 'node' parameter has none, and the description does not explain its purpose or format beyond the phrase 'configured on a Proxmox node'. The description fails to add meaning for the undocumented parameter, leaving ambiguity.

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 the tool lists TLS certificates on a Proxmox node, specifies read-only nature, and enumerates returned fields (filename, subject, issuer, validity dates, SANs, fingerprint). This distinguishes it clearly from sibling mutation tools like pve_node_cert_delete and pve_node_cert_upload.

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 explicitly marks the tool as 'read-only', providing clear context for when to use it. However, it does not mention when not to use it or cite alternatives (e.g., 'use pve_node_cert_delete to remove certificates'). Despite this, the read-only hint is a strong usage guideline.

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