connect_to_kernel

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the tool connects to an existing kernel, uses a connection file or environment variable fallback, and returns a status message. It does not mention side effects, idempotency, failure behavior, or whether an already-connected state matters.

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 concise and well-structured with a clear first sentence followed by Args and Returns sections. Every line adds useful information with no filler or repetition.

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 tool with one optional parameter and an output schema, the description covers the essential purpose, parameter semantics, fallback behavior, and return value. It omits edge cases like error handling or what happens if the connection file is invalid, but the basic invocation context is fully supplied.

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?

Schema description coverage is 0%, but the description compensates well for the single parameter by explaining that connection_file is the path to a kernel connection JSON file, is optional, and falls back to the IPYTHON_MCP_CONNECTION environment variable when not 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 opens with a specific verb and resource: 'Connect to an existing IPython kernel using its connection file.' This clearly differentiates it from sibling tools like execute_code, kernel_status, and interrupt_kernel, which serve obviously different purposes.

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 the tool is used to establish a connection to an existing kernel, and the fallback to the IPYTHON_MCP_CONNECTION environment variable provides some context. However, it does not explicitly state when to prefer this over siblings, such as before executing code, nor does it mention any exclusions or prerequisites.

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