pv_list

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

The readOnlyHint=true annotation already covers the safety profile, so the "[READ]" prefix adds nothing. The description does add value by listing the returned columns and explaining the default-target behavior, but omits scope (all namespaces vs one) and pagination behavior for what could be a large cluster-wide listing.

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 terse lines with the operation and return columns front-loaded; the Args stanza is compact and readable. The "[READ]" tag is redundant with the readOnlyHint annotation, a minor waste of the opening position.

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?

With one optional parameter, no output schema, and read-only annotations, the definition covers the essentials including return field names and the default-target fallback. Remaining gaps (namespace scope, pagination, sort order) are minor for a simple list tool.

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% and the schema only offers a bare "Target" string with default null, so the description must compensate — and it does, explaining that target is a k8s target name from config and that omission falls back to the default. That is meaningfully more than the schema alone provides.

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 and resource ("List persistent volumes") and enumerates the columns returned (name, capacity, status, claim, class, age). It is distinguishable from sibling pvc_list/statefulset_list by explicit resource noun, though it never names an alternative to disambiguate against.

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 when-to-use or when-not-to-use guidance and no named alternatives against ~50 sibling tools. The only procedural hint is "omit to use the default" for the target argument, which is parameter-level rather than task-level context.

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