k8s__list_pvcs

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

With no annotations provided, the description carries full behavioral disclosure responsibility. It correctly implies a read-only listing operation but does not elaborate on aspects like scope (e.g., all namespaces if none specified) or pagination. The behavior is minimally transparent.

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 a single, well-structured sentence that conveys the core function without redundant information. It is front-loaded and efficient.

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 the simplicity of the tool (one optional parameter, no output schema), the description is fairly complete. It names the resource and key fields, though it could optionally mention that omitting the namespace defaults to 'default' for completeness.

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?

The input schema has 100% coverage for its single 'namespace' parameter, so the description does not need to add additional parameter details. It does not enhance the schema's explanation, meeting the baseline expectation.

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 PersistentVolumeClaims and specifies the fields returned (status, capacity, accessModes, storageClass). It effectively distinguishes itself from sibling tools like k8s__list_pods or k8s__list_deployments by targeting a specific Kubernetes resource.

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 implies usage when you need to list PVCs but offers no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. Usage is inferred rather than explicitly directed.

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