download_cluster_kubeconfig

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

With no annotations, the description carries full burden. It discloses the result is a live credential with a bearer token, gives security instructions, and mentions revocability. It does not explicitly cover auth or rate limits, but the security context is strong.

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 front-loaded with the core action, then adds conditional, security, and return info in logical order. Slightly verbose but each sentence earns its place.

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 no output schema, the description explains the return type (raw kubeconfig YAML). It also covers prerequisites, security handling, and error conditions. Fully complete for a 2-parameter read operation.

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 value by explaining the parameter provenance (from list_cluster_kubeconfigs) and the active-credential constraint, which is not in the schema.

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 uses a specific verb ('Re-download') and resource ('LONG-LIVED kubeconfig credential'), and explicitly distinguishes from the sibling tool get_cluster_kubeconfig by contrasting long-lived vs short-lived credentials.

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 clearly states when to use this tool ('for standing automation that must keep working'), when not to use ('revoked or expired credentials return an error'), and explicitly names the data source for parameters (list_cluster_kubeconfigs).

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