kubectl_context

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

The description states the tool can 'set the current context', which is a write/mutating operation, but the annotations declare readOnlyHint=true, indicating a read-only expectation. This is a direct contradiction, severely reducing transparency. Without annotations, the set operation would require more detail about side effects, but here the contradiction is the primary issue.

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 that front-loads the main purpose. It is concise and to the point, with no superfluous words. It could be slightly more informative without adding length, but it is well-structured.

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 complexity (multiple operations including a mutating 'set'), the description lacks details about return values, prerequisites, or side effects. The contradiction with annotations further undermines completeness. No output schema is provided, so the description should cover behavioral expectations but fails to do so adequately.

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 has 100% description coverage for all 5 parameters, so the schema already explains each parameter. The tool description does not add additional meaning beyond the schema, meeting the baseline. No extra value is provided.

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's purpose: 'Manage Kubernetes contexts' and enumerates the specific operations (list, get, set), providing a specific verb and resource that distinguishes it from sibling tools like kubectl_get or kubectl_describe.

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 implies when to use the tool (for managing contexts) but does not provide explicit guidance on when not to use it or suggest alternatives. The usage context is clear from the tool name and schema, but no exclusions or conditions are mentioned.

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