pvc_get

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves details (implying read-only), but doesn't disclose behavioral traits like error handling (e.g., what happens if the PVC doesn't exist), authentication needs, rate limits, or the format of returned details. For a read operation with zero annotation coverage, this leaves significant gaps.

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 appropriately sized and front-loaded: the first sentence states the purpose clearly, followed by structured Args and Returns sections. There's no wasted text, though the Returns section is vague ('Detailed information')—this is a completeness issue, not conciseness. The structure aids readability without being verbose.

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 tool's moderate complexity (3 required parameters, no output schema, no annotations), the description is incomplete. It lacks details on error conditions, output format, and usage context (e.g., how it differs from pv_get). While it covers the basic purpose and parameters, it doesn't provide enough information for reliable agent invocation in a Kubernetes environment with many sibling tools.

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 schema provides no parameter descriptions. The description lists the three parameters with brief explanations (e.g., 'The Kubernetes context name'), adding basic semantics beyond the schema's titles. However, it doesn't elaborate on format, constraints, or examples (e.g., valid namespace patterns), leaving room for improvement. With 0% coverage, this partial compensation justifies a baseline 3.

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's purpose with a specific verb ('Get details') and resource ('PersistentVolumeClaim'). It distinguishes itself from siblings like pvc_list (which lists multiple) and pvc_create/delete/update (which modify). However, it doesn't explicitly contrast with pv_get (which gets PersistentVolumes) or other *_get tools, keeping it at a 4 rather than 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. It doesn't mention when to choose pvc_get over pvc_list (for details of a specific claim vs. listing all), nor does it reference prerequisites like needing the PVC to exist. The agent must infer usage from the tool name and parameters alone.

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