pve_node_certificates

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

Explicitly states 'READ-ONLY' and 'No state change.' Describes return format in detail: filename, subject, issuer, validity dates, SANs, fingerprint. With no annotations, this full disclosure is excellent.

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?

Three sentences: purpose and read-only, return format, alternatives. No wasted words, front-loaded with core purpose.

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?

Well-contextualized with sibling tools and return format. Lacks prerequisites or error info, but has output schema. Very complete for a list 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 coverage is 100% with descriptions for both parameters. The description does not add extra meaning beyond the schema, so baseline 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?

Description starts with 'READ-ONLY: list TLS certificates configured on a Proxmox node,' clearly stating verb, resource, and scope. It explicitly distinguishes from sibling tools pve_node_cert_upload and pve_node_cert_delete.

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?

Provides explicit alternatives: 'To add or replace a certificate use pve_node_cert_upload; to remove one use pve_node_cert_delete.' Clearly indicates when to use this tool (list) and when to use others.

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