storage_content

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

No annotations provided, description implies read-only (listing) but does not explicitly state non-destructive nature. Adds filtering context but no mention of permissions or side effects.

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 sentences directly stating purpose and filtering details. Concise and structured well, though could be slightly more front-loaded.

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?

Given parameter count (3, 2 required) and output schema present, description explains purpose, filter, and required inputs. Adequate for a listing tool.

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 0%, but description adds significant meaning: explains 'content' filter options (vztmpl, iso, backup, images, rootdir) and mentions node and storage requirements.

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?

Description clearly states 'List what's stored on a storage pool' with specific resource types, and distinguishes from siblings like 'storage' which likely lists pools.

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?

Provides context: 'Useful for finding a template/ISO volid or seeing which disk images live on a pool. Needs the node and the storage id (from `storage`).' Lacks explicit alternatives but usage is clear.

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