delete_sessionPermanently delete a thinking session by specifying its name in category:name:subcategory format. Use this to remove sessions you no longer need.
Delete a thinking session permanently.
| Name | Required | Description | Default |
|---|---|---|---|
| sessionName | Yes | Session name to delete (format: category:name:subcategory) |
Changes observed during successful MCP inspections.
v1.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and 'permanently' does convey irreversibility, which is the key behavioral fact for a delete. However, it does not state permission requirements, whether the session must exist first, or the consequence for related thoughts, leaving notable gaps and forcing some inference.
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?
A single short sentence with the key constraint ('permanently') front-loaded. No wasted words, though brevity leaves little room for the routing detail an agent would need.
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 destructive mutation tool with no annotations, no output schema, and a destructibility claim that should be fleshed out, this is too thin. It should say whether the operation is recoverable, what permissions or preconditions apply, and how it differs from cleanup_sessions.
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 100%, so the schema already documents sessionName and its category:name:subcategory format. The description adds nothing about the parameter, which is acceptable given the high coverage, so a baseline 3 is appropriate.
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?
States a specific verb (delete) and resource (a thinking session), and adds the scope 'permanently'. It doesn't name a sibling like cleanup_sessions, which also relates to session removal, so an agent cannot fully distinguish the two from the description alone.
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?
No when-to-use guidance, no prerequisites, and no mention of the sibling cleanup_sessions or rename_session. The permanent nature hints at a caution condition but offers no explicit alternative or exclusion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.