proxmox_get_nodes

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly indicates a read-only operation ('List') and the scope ('all nodes in the cluster'), but it does not disclose potential prerequisites (e.g., authentication), output format, or any edge cases. However, the operation is simple and the description does not mislead.

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 a single concise sentence that contains no redundant information and fully captures the tool's purpose. It is properly structured and front-loaded.

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 simplicity of the tool (no output schema, one parameter), the description is mostly complete for an agent to know what the tool does. However, it does not specify what information is returned for each node or explicitly differentiate from proxmox_node_status, leaving slight room for ambiguity.

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 schema provides the only parameter device_id with a description, so schema coverage is 100%. The description adds some context that the device_id likely refers to a Proxmox server from which the cluster is queried, but it does not provide additional parameter-specific details beyond the schema.

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 all nodes in the Proxmox cluster' uses a specific verb (list) and resource (nodes), and clarifies the scope (the cluster). This distinguishes it from sibling tools like proxmox_node_status, which likely targets a specific node.

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 clearly implies when to use the tool (when you need to list all nodes in a Proxmox cluster), but it does not explicitly mention alternatives or situations when this tool should not be used. The usage is obvious from the wording but lacks direct comparison to related tools.

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