Get VM RRD time series

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the tool is safe. The description adds that it returns raw RRD metrics and lists some metrics, which adds context but doesn't reveal additional behavioral traits like pagination or response size.

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 two sentences, front-loaded with the action (Return raw RRD metrics) and purpose (Used for charting and capacity analysis). No redundant information.

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 low schema coverage, the description is somewhat minimal. It tells what the tool returns but not the format or how parameters affect output. For a charting tool, it may be adequate but lacks full context.

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 coverage is only 20% (only 'ds' has a description). The description adds examples of data sources (cpu, mem, netin/out, diskread/write) which clarifies the 'ds' parameter, but does not explain 'node', 'vmid', 'cf', or 'timeframe' beyond implying a timeframe. It adds some value but is not comprehensive.

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 it returns raw RRD metrics (cpu, mem, netin/out, diskread/write) for a VM at a given timeframe, and is used for charting and capacity analysis. This distinguishes it from siblings like get_vm_rrddata or get_container_rrd.

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 usage for charting and capacity analysis but provides no explicit guidance on when not to use it or alternatives. No exclusions or comparisons to sibling tools are given.

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