close_sessionPermanently remove a skill session and its execution state from the runtime, returning the final state snapshot for auditability before deletion.
Housekeeping: permanently remove a skill session and its execution state from the runtime. Returns the final Σ snapshot for auditability before deletion.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | Identifier of the session to remove from the runtime. |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so well: it states that removal is permanent, that execution state is deleted, and that a final snapshot is returned for auditability. This gives the agent the key safety and side-effect information before invocation.
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 a single, efficient sentence that front-loads the action and consequence before mentioning the return value. Every phrase earns its place without fluff.
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 simple one-parameter destructive tool with no annotations or output schema, the description covers the essential context: what is removed, that it is permanent, and what the caller receives. Nothing critical is missing for correct invocation.
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 session_id parameter already documents itself as the identifier of the session to remove. The description adds no additional parameter-level semantics, so the baseline of 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?
The description uses a specific verb-resource pair, 'permanently remove a skill session and its execution state,' and labels itself as housekeeping, making the teardown purpose unmistakable. It also distinguishes itself from siblings like initialize_skill and execute_step by focusing on session termination rather than setup or execution.
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 'Housekeeping' framing clearly signals that this tool is for cleanup and session removal, which gives an agent the context to choose it when a session is no longer needed. It does not explicitly name exclusions or alternatives, but the lifecycle role is clear enough given the sibling set.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.