pvc_list

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

Annotations already declare readOnlyHint=true, and the '[READ]' tag merely repeats that. The description does add useful context by listing what each claim returns, but says nothing about pagination, volume of results, or auth/target resolution beyond the arg hint.

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?

One front-loaded sentence with the verb, resource, and returned fields, followed by a terse Args block. No filler, though the '[READ]' tag is redundant with annotations.

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?

For a read-only two-param list tool with no output schema, the description covers both parameters and enumerates the fields returned, which is sufficient for correct invocation. Minor gaps remain around result size/pagination but are not blocking.

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 0%, so the description carries the burden and largely does: it explains namespace omission semantics and that target is the 'k8s target name from config'. Both params are covered, though no format/example for the target string is given.

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?

States a specific verb+resource ('List persistent volume claims') and even enumerates the returned fields (name, status, capacity, class, age). It is clearly distinguishable from pv_list and storageclass_list by resource, though it does not explicitly call out the sibling boundary.

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?

'omit for all namespaces' gives a clear conditional for the namespace argument, which implies when to scope vs. not. However there is no explicit when-to-use vs. pvc_get or other storage listing alternatives, so usage is only implied.

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