List Storage Overview

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

The description discloses it is read-only and lists multiple resource types with phase flags. Since no annotations are provided, the description carries the full burden and adequately conveys the safe, non-destructive nature of the 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?

The description is two sentences with no wasted words. It front-loads the main resources and critical behavior, making it easy to parse quickly.

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 no output schema, the description does not detail return format but mentions phase flags, which is helpful. For a simple list tool with one optional parameter, the description is sufficiently complete for an agent to invoke correctly.

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 100%, so the parameter is already well-documented. The description adds minimal extra meaning beyond what the schema provides ('If set, only list PVCs in this namespace'), essentially paraphrasing it. Baseline 3 is appropriate.

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 lists StorageClasses, PVCs, PVs, and VolumeAttachments with phase flags. It uses a specific verb (list) and resource (storage overview) and distinguishes from sibling tools that list other resources (e.g., pods, services).

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 provides clear usage guidance by explaining how the namespace parameter affects PVC listing ('Omit namespace to list PVCs in all namespaces'). It lacks explicit when-to-use vs alternatives, but no sibling tool covers this specific storage overview.

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