k8s_get_pvs

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

No annotations provided; description only lists output fields. Missing behavioral traits like read-only nature, required permissions, or side effects. 'List' implies read-only but not explicit.

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?

Single sentence, 15 words, efficient and well-structured. Front-loaded with key action and resource.

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?

Simple tool with one parameter; description explains return values but fails to document the input parameter. Adequate for basic understanding but incomplete on context.

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 has 0% coverage; only parameter 'context' is listed. Description does not explain what 'context' means (e.g., kubeconfig context). No added semantic value.

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 resource 'PersistentVolumes' with details on returned information (capacity, access modes, etc.). It distinguishes from sibling tools like k8s_get_pvcs.

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?

No explicit guidance on when to use this tool vs alternatives. No prerequisites or exclusions mentioned. Implied usage for listing PVs but no context.

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