issue_tkc_kubeconfig

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true): it discloses the embedded Supervisor JWT bearer token and its expiry, recommends output_path to keep the token out of agent context, and warns that output_path creates parent dirs and truncates the file at 0600 (e.g. '~/.kube/config' clobbers the user's kubeconfig). One mild tension worth noting: it describes a file overwrite while destructiveHint=false, but the description explicitly scopes that claim ('Nothing in the managed cluster changes') and its disclosure makes the risk visible rather than hiding it, so this is added safety context, not a contradiction.

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?

Front-loaded with the [WRITE] credential-access label and the core action in the first line, and the routing/alternative guidance is in the final line. Dense parentheticals and em-dash clauses make it heavy to scan, but essentially every sentence carries unique, load-bearing information.

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?

No output schema exists, yet the description states the return shape both ways ({cluster, kubeconfig} vs {cluster, written_to}), documents the credential's lifetime, the safety-relevant side effects, and the required sequencing. An agent has everything needed to call this correctly and handle the result.

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 the baseline is 3. The description still adds value beyond the schema for output_path (creates parent directories, truncates the target, writes owner-only 0600, and the strong 'always pass output_path' recommendation) and states the return-shape difference between providing and omitting it. 'target' is left entirely to the schema, so it is not a full 5.

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: 'issue a kubeconfig for one TKC cluster', tagged [WRITE] and 'Credential access'. It explicitly distinguishes itself from the closest sibling by naming issue_supervisor_kubeconfig as the Supervisor-level alternative, so an agent can route without opening either schema.

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?

Gives an explicit when ('only when the user explicitly asks') and when-not ('never as a side step'), names the prerequisite ('Run list_tkc_clusters first for name and namespace'), and names the alternative for the adjacent use case. Nothing is left to inference.

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