get_storage_rrddata

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

No annotations are provided, so the description must fully characterize behavior. It indicates a read-only operation (getting stats) but does not disclose potential side effects, authentication requirements, rate limits, or output structure beyond the vague 'usage over time'. This is insufficient for an agent to fully understand the tool's behavior.

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 with 4 short sentences, including a structured Args block. Every sentence provides essential information without waste. It is front-loaded with the purpose.

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?

The description covers purpose and parameters but does not describe the output format, despite an output schema existing. It mentions 'usage over time' but lacks detail on what the returned data looks like (e.g., timestamps, metrics). Adequate but not fully complete.

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 has 0% description coverage, but the description adds clear explanations for each parameter: 'node' is the node name, 'storage' is the storage ID, and 'timeframe' with valid values. This adds significant meaning beyond the schema titles and default.

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 retrieves RRD statistics for a storage pool over time. The verb 'get' and resource 'storage pool RRD statistics' are specific and distinguish it from related tools like get_storage_config or get_storage_volume_info.

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 lists parameters and timeframe options, implying when to use it (for historical usage data), but does not explicitly state when to use this tool versus alternatives. No exclusion or alternative guidance is provided.

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