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

Annotations already establish this as a read-only operation, so the description's job is to add context. It discloses that unbound claims sort first and that a list response carries total, returned, truncated and scope, which is useful behavioral detail. It does not cover permissions, rate limits, or error behavior beyond the scope_required constraint shown in the schema.

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?

Three sentences, front-loaded with the operation and returned fields; the sorting rule and list requirements follow efficiently. Every sentence contributes a distinct piece of information, with no filler.

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 no output schema, the description carries the return-value burden and does a good job listing row fields and list metadata (total, returned, truncated, scope). The only gap is that it does not explicitly route among sibling resource getters, but for calling this tool correctly that is minor.

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 100%, so the schema already documents name, namespace, cluster_id and all_namespaces including the list requirement. The description repeats the namespace/all_namespaces rule and does not add syntax, constraints, or examples beyond the schema, so the baseline of 3 is appropriate.

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 ('Fetch') and resource ('PersistentVolumeClaim summary rows'), and enumerates the returned fields, so the agent knows exactly what data comes back. It does not name a sibling tool or say when this is preferable to get_pods/get_configmaps, so it misses the top of the scale.

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 gives the call-shape constraint for list vs named read ('A list needs namespace or all_namespaces=true... a named read needs neither'), which helps the agent avoid the scope_required error. It does not say when to choose get_pvcs over other resource getters or give exclusion conditions, so usage guidance remains implied rather than explicit.

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