pve_get_node_rrddata

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

With no annotations, the description must fully disclose behavior. It mentions 'historical metrics' and 'over time', implying time-series data and a read-only operation, but it does not explicitly state that there are no side effects, nor does it describe the response structure, aggregation, or any rate-limit or permission requirements.

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 is front-loaded with the primary purpose and includes the key resource (node) and metric types. No unnecessary words.

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?

Despite having an output schema, the description leaves important context unaddressed: usage guidance, parameter semantics, and behavioral nuances. For a tool with no annotations, this sparse description is incomplete for an agent to select and invoke it with confidence.

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 description coverage is 0%, so the description must compensate. However, it does not explain the 'node' or 'timeframe' parameters at all, nor does it elaborate on the enum values (hour/day/week/month/year). The phrase 'over time' weakly hints at timeframe, but adds no concrete meaning 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 clearly states what the tool returns: historical metrics for a node, including CPU, RAM, net, and disk over time. It distinguishes from sibling tools like pve_get_node_status (current status) and pve_get_vm_rrddata (VM-specific) by specifying 'node' and 'over time', though it does not explicitly name alternatives.

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. It does not mention that this is for historical time-series data as opposed to current status, nor does it reference sibling tools such as pve_get_node_status or pve_get_vm_rrddata.

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