restart_kernel

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

No annotations, so description fully carries burden. Clearly states it clears all variables, definitions, and state, and returns a confirmation. Discloses destructive nature.

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?

Two concise paragraphs, first sentence clearly states action, second adds context. No wasted words.

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 no parameters and simple action, description covers what, when, and return. Output schema exists, so return value detail is 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?

No parameters, input schema is empty with 100% coverage. Baseline 4 as per instructions; description need not add parameter info.

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 uses specific verb 'restart' and resource 'kernel', explicitly stating it clears all state. Distinguishes from siblings like 'clear_variables' by calling it the 'nuclear option'.

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 says 'Use when the kernel is in a bad state or you need a fresh start.' Provides clear context, though alternatives are not explicitly listed.

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