pve_list_node_certificates

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

No annotations are provided, so the description must fully disclose behavior. It only states the action without any details on output format, permissions required, rate limits, or whether it's a read-only operation. This leaves critical behavioral traits unspecified for a tool that likely interacts with system certificates.

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 at three words, with no wasted language. It front-loads the core action ('List') and resource ('node certificates'), making it easy to parse quickly, though this brevity contributes to gaps in other dimensions.

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 no annotations and no output schema, the description is incomplete for a tool that likely returns structured certificate data. It fails to explain what 'certificates' entail (e.g., types, fields) or behavioral aspects, leaving significant uncertainty for an agent trying to use it effectively in a complex system like Proxmox VE.

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%, with the single parameter 'node' clearly documented as 'Node name'. The description adds no additional semantic context beyond what the schema provides, such as examples or constraints, but the schema adequately covers the parameter, meeting the baseline for high coverage.

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 'List node certificates' restates the tool name 'pve_list_node_certificates' almost verbatim, making it tautological. It specifies the verb 'list' and resource 'node certificates', but doesn't clarify what 'node certificates' are or how this differs from other certificate-related tools like 'pve_order_node_certificate' or 'pve_renew_node_certificate' among the siblings.

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 guidance is provided on when to use this tool versus alternatives. With many sibling tools for listing various resources (e.g., 'pve_list_nodes', 'pve_list_node_networks'), there's no indication of context, prerequisites, or comparisons to help an agent choose appropriately.

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