kubectl_reconnect

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

Description explains behavior: recreates all API clients, forces fresh DNS resolution, and new TCP connections. It adds context beyond the readOnlyHint annotation (false), indicating mutation. While it doesn't detail potential disruptions, it adequately discloses the reconnect action.

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?

Single sentence that is front-loaded with purpose and then provides usage context. No extraneous words; every part adds value.

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?

Description is complete for this simple tool: explains what, when, and why. No output schema exists, but return format is not critical for a reconnect action. Missing mention of potential side effects (e.g., brief disruption) but overall sufficient.

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?

Input schema has zero parameters with 100% coverage, so description needs no parameter details. Baseline of 4 is appropriate as description adds no parameter-specific info, but none is needed.

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?

Description clearly states verb 'reconnect' and resource 'Kubernetes API server by recreating all API clients'. It provides specific context of cluster upgrades, distinguishing it from other kubectl tools that perform different actions.

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?

Explicitly states when to use: after cluster upgrades (e.g., EKS control plane upgrades). Does not specify when not to use or list alternatives, but given the tool's unique purpose, no exclusion is necessary.

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