storage_content

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

Labels the operation with '[READ]' indicating a safe, non-destructive action. With no annotations provided, the description effectively communicates the read-only nature and basic behavior, though it omits details like required permissions or error conditions.

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?

Extremely concise: one-line summary followed by clear parameter definitions. No wasted words; each sentence adds distinct value. Front-loaded with the core 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?

Covers purpose, parameters, and a cross-reference to storage_list. Lacks description of return format or pagination, but given the tool's simplicity and no output schema, the description is sufficiently complete for basic usage.

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?

With 0% schema description coverage, the description fully compensates by explaining all four parameters: storage (with cross-reference), content (with explicit filter values), target (config-based), and node (default behavior). This is essential for correct usage.

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 tool lists volumes (ISOs, disk images, backups, templates) on a storage pool. It differentiates from sibling tool storage_list (which lists pools) by specifying the resource type and content filters.

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 parameter context but no explicit when-to-use or when-not-to-use guidance. It references storage_list for the storage id, implying a prerequisite, but does not compare with other list tools or suggest alternatives.

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