restart

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

The description outlines the behavioral sequence (killing running executions, stopping old kernel, creating new kernel) and explicitly notes that execution history is preserved. It also addresses the edge case of a running execution. However, it does not mention potential side effects on non-persistent state or any error handling beyond return values.

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, well-structured with a clear purpose and a separate section for the reset boundary. It avoids unnecessary verbosity while covering key behavioral aspects.

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 description includes explicit return values (new kernel status and PID, or error on failure) and covers the main execution conditions. It is complete for an agent to understand the tool's output without additional information.

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 tool has no parameters, and the schema coverage is 100%, so the baseline is 3. The description does not need to explain parameters, and it correctly omits them.

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 function: restart the IPython kernel while preserving execution history. It specifies the verb (restart) and the resource (IPython kernel), and it is distinct from sibling tools like run_cell or interrupt.

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 does not explicitly mention when to use this tool versus alternatives. It implies usage for restarting the kernel but lacks guidance on scenarios where this is preferable to other tools.

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