k8s_get_pvcs

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

With no annotations, the description carries full behavioral burden. It explains the namespace behavior, but does not disclose permission requirements, pagination limits, or effects of the context parameter. It is adequate for a simple list operation.

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, front-loaded with purpose and a key behavior. No wasted words, but could be slightly more structured to cover all parameters.

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?

Core purpose and namespace behavior are covered, but context and label_selector are not explained, and output format is only partially listed. Given no output schema, more detail on return could help 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?

Schema has 0% coverage, so description must compensate. It explains namespace behavior ('omit for all namespaces') but leaves context and label_selector unexplained. Partial value added.

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 states the tool lists PersistentVolumeClaims and specifies the returned fields (status, capacity, access modes, storage class). It clearly distinguishes from siblings like k8s_get_pvs (PersistentVolumes) and other get tools by naming the specific 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?

No guidance on when to use this tool versus alternatives (e.g., k8s_get_pvs, k8s_get_storage_classes). The hint about omitting namespace is a usage tip but not a comparative guideline.

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