pvc_list

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

With no annotations provided, the description carries full burden but only states it's a list operation. It doesn't disclose behavioral traits like whether it requires specific permissions, returns paginated results, handles errors, or provides 'basic information' details. For a read operation in Kubernetes with zero annotation coverage, this is insufficient.

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 perfectly structured and concise: purpose statement, parameter documentation, and return value description in three clear sections. Every sentence earns its place with zero wasted words.

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 simple list tool with 2 parameters and no output schema, the description covers the basics but lacks important context. It doesn't explain what 'basic information' includes, doesn't mention error handling or permissions, and doesn't differentiate from sibling tools. With no annotations, it should provide more behavioral context for adequate 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 description explicitly documents both parameters ('context_name' and 'namespace') in the Args section, adding clear meaning beyond the schema which has 0% description coverage. This fully compensates for the schema gap, though it doesn't explain parameter formats or constraints beyond naming them.

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 ('PersistentVolumeClaims') with scope ('in a given namespace'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'pvc_get' or 'pv_list', which would require a 5.

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 provides no guidance on when to use this tool versus alternatives like 'pvc_get' (for single PVC details) or 'pv_list' (for PersistentVolumes). It mentions the namespace parameter but doesn't explain usage context or prerequisites.

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