revoke_cluster_kubeconfig

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

Description adds significant context beyond the destructiveHint annotation: explains the internal mechanism (deletes ServiceAccount), the immediate effect (token stops working), and the irreversible impact ('breaks any automation'). No contradiction with annotations.

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 succinct sentences with no filler. Front-loads the critical action and key constraints. Every sentence serves a purpose.

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?

Covers purpose, usage, parameter sources, safety, and destructive nature. Lacks mention of return value or success indicators, but given the destructive action, this is acceptable. Complete enough for an agent to use correctly.

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 100%, so baseline is 3. The description adds the source for service_id and credential_id (from list_cluster_kubeconfigs) and reinforces the confirm safety requirement, but does not add new semantic details beyond what the schema descriptions already provide.

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 action ('Revoke'), the resource ('LONG-LIVED kubeconfig credential'), and the mechanism ('deletes the underlying ServiceAccount'), distinguishing it from sibling tools like create_cluster_kubeconfig or list_cluster_kubeconfigs.

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?

Provides explicit context: requires scope services:write, is irreversible, requires user approval via confirm:true, and specifies that parameter values come from list_cluster_kubeconfigs. Does not explicitly state when not to use, but gives sufficient guidance.

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