proxmox_guest_rrddata

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It states it returns RRD data, but it does not clarify data freshness, rate limits, handling of missing VMs, or that it is a read-only operation. The description is minimally adequate.

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, clear sentence that front-loads the purpose with no extraneous words. It is appropriately concise for a straightforward retrieval tool.

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?

With 5 parameters, no output schema, and no annotations, the description is too sparse. It does not explain the meaning of 'RRD data', how 'timeframe' and 'cf' relate to the returned data, or what format the response will be. An agent would need additional context to invoke this correctly.

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 high (80%): four of five parameters have descriptions, and the 'type' parameter has an enum limiting values. The description adds little beyond the schema—it confirms 'type' is vm or lxc, but this is already given. Therefore, it meets the baseline but does not significantly enhance understanding.

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 verb 'Get' and the resource 'performance metrics (RRD data)', and explicitly distinguishes between VM and LXC container types (type=vm or type=lxc). This directly differentiates it from sibling tools like proxmox_guest_status or proxmox_guest_config, which focus on different data.

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 implies the tool is for retrieving performance metrics, but it does not provide explicit guidance on when to use it versus alternatives, nor does it mention when not to use it or any prerequisites. With many sibling tools, more context would be helpful.

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