kubectl_context

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

The description includes 'set' as an operation, implying a write action, but the annotation readOnlyHint is true, which is contradictory. The description should clarify that the set operation changes the current context, but annotations claim read-only.

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 a single sentence but lacks structure; it does not separate operations or provide a clear hierarchy. While concise, it omits important details and does not justify its brevity with completeness.

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 the tool's complexity (5 parameters, 3 operations) and no output schema, the description is insufficient. It fails to explain return values, side effects (e.g., setting context), or behavioral nuances for each 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?

The input schema covers all 5 parameters with descriptions, achieving 100% coverage. The description adds no additional meaning beyond what the schema already provides, so a baseline score 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?

The description clearly states the tool manages Kubernetes contexts with three specific operations: list, get, and set. It distinguishes from sibling tools like kubectl_get, which are for resource retrieval, not context management.

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?

No guidance on when to use this tool versus alternatives. It does not specify prerequisites, limitations, or when to choose kubectl_context over other kubectl tools.

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