list_pvcs

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 only states the action ('list all') with no disclosure of pagination, permission requirements, or whether the operation is strictly read-only (though 'list' implicitly suggests it). Adds little beyond the literal function.

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?

Single sentence with zero filler, immediately conveying the core function. Every word earns its place and the description is front-loaded with the verb 'List'.

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?

Tool is simple, but with two optional parameters and no parameter descriptions, the description does not explain cluster_alias or the namespace default. Output schema exists, but the operation's full semantics (e.g., cluster selection) are not covered, and the description is too sparse to compensate for the missing annotation context.

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 coverage is 0%, and the description does not mention 'namespace' or 'cluster_alias' parameters at all. The agent must guess that 'in a namespace' maps to the namespace parameter, and cluster_alias is entirely unexplained, leaving the agent without essential information to invoke the tool correctly.

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?

Specific verb+resource+scope ('List all PersistentVolumeClaims in a namespace'), clearly distinguishes from the sibling get_pvc by emphasizing 'all' rather than a single 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?

Implied usage: use when you need to enumerate all PVCs in a namespace. No explicit comparison with get_pvc or mention of when not to use it, despite having a sibling tool that retrieves a single PVC.

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