Storage content

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds the types of volumes listed and filtering capability, but does not elaborate on openWorld behavior (returning more data than requested) or other traits like pagination. It provides some added context beyond annotations but is not rich.

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?

Two clear, front-loaded sentences with no wasted words. Every sentence provides meaningful information about the tool's action and usage.

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?

For a read-only list tool with annotations and schema covering required parameters, the description is adequate. It states what is listed and how to filter. However, it does not mention the openWorldHint behavior or provide any return value format, which would be useful given no output schema.

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 67%; node and content have descriptions, storage does not. The description mentions content types and filtering, adding value to the content parameter but not addressing the missing storage parameter description. It compensates partially but not fully.

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 'List' and the resource 'volumes on a storage,' specifying the types of content (ISO images, container templates, disk images or backups). This distinguishes it from sibling tools like pve_list_storage (which lists storage definitions) and pve_list_backups (backup-specific).

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 indicates using the content filter to narrow results, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools among siblings. The context is implied but not explicit.

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