proxmox_cluster

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

With no annotations provided, the description carries the full burden. It correctly identifies read vs write behavior ('Query' for status/options, 'update' for update_options) and notes permission requirements for the write action. However, it does not disclose side effects, rate limits, or error conditions.

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: a single opening sentence followed by pipe-separated action details. Every word earns its place, with no repetition or filler.

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 tool's low complexity (two parameters, no output schema), the description covers the return values for each action (e.g., status returns 'overall cluster status with nodes and resource usage'). It lacks prerequisite details for read actions but is sufficient for basic use.

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?

The description adds meaning to the 'action' parameter by explaining each enum value. For the 'options' parameter, it repeats the schema description ('Cluster options to update') without additional detail. With 50% schema coverage, the description partially compensates but does not fully clarify the options object's structure.

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's purpose ('Query Proxmox cluster info') and enumerates specific actions (status, options, update_options). While it doesn't explicitly name sibling tools, the verb and resource ('cluster info') distinguish it from more specific cluster tools like proxmox_cluster_backup_job or proxmox_cluster_firewall.

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 provides explicit context for each action, including a permission note for 'update_options' ('requires elevated permissions'). It does not, however, state when not to use this tool or list alternative tools for similar tasks.

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