k8s_disconnect

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to state side effects (e.g., whether the session is terminated, resources cleaned up), idempotency, or whether it is reversible. The single sentence is insufficient for a state-changing operation.

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, front-loaded sentence with no wasted words, but it is under-specified. While conciseness is achieved, the lack of substance means it does not earn its place in providing useful guidance.

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?

The tool is simple but has side effects (disconnecting a session) and an output schema. The description does not explain return values, failure modes, or what happens after disconnection. Without annotations or schema descriptions, the agent lacks essential context for correct invocation.

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 schema has one parameter (session_name) with a default, but schema description coverage is 0% and the description does not mention it at all. The description adds no meaning to the parameter, leaving the agent to infer its purpose from the name alone.

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 'Drop a Kubernetes session' uses a specific verb ('Drop') and names the resource ('a Kubernetes session'), clearly indicating it is the inverse of k8s_connect. While 'session' is somewhat vague, the sibling context makes the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives like k8s_connect or k8s_status. It does not mention prerequisites, session lifecycle, or any conditions that would trigger its use.

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