devtools_show_kubeconfig

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

With no annotations, the description carries the disclosure burden and it delivers: 'Show' signals a non-mutating operation, and the OUTPUT_DESCRIPTION explicitly details status, stdout with the kubeconfig path/instructions, stderr, and exit_code. It also notes the prerequisite state, so an agent knows what to expect.

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 first sentence is a front-loaded summary, and the structured metadata (USECASE, INSTRUCTIONS, OUTPUT_DESCRIPTION, PREREQUISITES) is compact and useful. There is minor redundancy with TOOL_NAME and DISPLAY_NAME repeating the title, but the overall block remains efficient.

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?

For a zero-parameter informational tool, the description is complete: it covers what the tool does, when to use it, prerequisites, output shape, and a related tool. The presence of an output schema further covers return value structure, so nothing critical is missing.

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?

There are zero parameters and the schema is empty, so the baseline is 4. The description reinforces this with 'INPUT_DESCRIPTION=none' and the example call devtools_show_kubeconfig(), leaving no ambiguity about invocation.

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 opening sentence names a specific action ('Show') and resource ('kubeconfig location and access instructions') scoped to the SNO cluster, which clearly separates it from sibling tools such as devtools_show_config. The purpose is immediately understandable and not a tautology.

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 explicitly states when to call this tool: 'Call after deploy_sno' and lists the prerequisite 'deploy_sno has run.' It does not explicitly name alternative tools or when-not conditions, but the temporal constraint gives clear usage context.

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