cleanup_sessionsDelete old thinking sessions by age to free storage. Specify a maximum age in days and remove outdated session data from the workspace.
Manually clean up old thinking sessions based on age.
| Name | Required | Description | Default |
|---|---|---|---|
| maxAgeDays | No | Maximum age in days before sessions are deleted |
Changes observed during successful MCP inspections.
v1.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies destruction (the param text says sessions are 'deleted') but never states irreversibility, scope (all sessions vs. this user/workspace), or required permissions for a destructive bulk 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?
A single compact sentence with no waste, and the scope ('old ... based on age') is front-loaded. It is perhaps too terse given it is a destructive tool, but nothing is redundant.
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?
With no annotations and no output schema, the description is the only place an agent could learn about irreversibility, scope of deletion, or what the return looks like — and it covers none of these. For a destructive cleanup tool this is a substantial gap.
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% and the single parameter is fully documented there, including default 90 and minimum 1. The description's 'based on age' adds nothing the schema doesn't already say, so baseline 3 applies.
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 (clean up) and resource (old thinking sessions) qualified by an age criterion, so the agent knows roughly what the tool does. It does not explicitly distinguish itself from the sibling delete_session, which also removes sessions, so the boundary is left to inference.
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?
'Manually' hints that this is the on-demand counterpart to some automatic sweep, but the description never says when to prefer this over delete_session or what preconditions apply. No alternatives or exclusions are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.