pve_storage_content

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

Clearly declares 'READ-ONLY' and 'No state change'. Mentions return fields (volid, size, content type). No behavioral contradictions with annotations (none provided). Lacks mention of pagination or limits, but acceptable for a simple list tool.

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?

Three sentences covering purpose, usage guidelines, and return value context. Front-loaded with core purpose, no wasted 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?

Covers essential aspects for agent usage: read-only, filtering, output purpose. Does not detail 'node' or 'proximo_target' parameters, but these are documented in schema. Overall sufficient given output schema presence.

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 100%, but description adds value by explaining content filter values (iso, vztmpl, backup) and contextual use of output (finding volid for restore/clone). This goes beyond schema descriptions.

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 starts with 'READ-ONLY: list the volumes a storage holds — ISO images, container templates, backups, disks', clearly specifying verb (list), resource (volumes/storage content), and scope. It distinguishes from sibling tools like pve_storage_create by explicitly noting 'To *define* a new storage use pve_storage_create'.

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?

Explicitly states 'No state change' and 'Optionally filter by content type... omit to list all'. Provides use case: 'use it to find a volid to pass to restore/clone tools' and directs to pve_storage_create for defining new storage.

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