End a SkillGild session when the task is complete, preventing further tool calls from being used. Use it to close out work and invalidate the session.
End a SkillGild session when the task is done, so its remaining tool calls can no longer be used.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | session ID from skillgild_start_session |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, and it does disclose the key consequence: remaining tool calls can no longer be used. It omits idempotency, permission requirements, and what happens on an invalid or expired session_id, which matter for a lifecycle-terminating mutation.
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?
One sentence, front-loaded with the action and the reason, with zero filler. It conveys purpose, timing, and consequence without repetition.
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 single-parameter lifecycle tool with no annotations or output schema, the description covers the essential outcome but leaves failure modes, idempotency, and post-end behavior of the session unspecified. It is adequate rather than complete.
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?
Only one parameter, and the schema already documents it at 100% coverage, including its provenance from skillgild_start_session. The description adds no further meaning about format or validation beyond the schema, so the 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?
The description names a specific verb (End) and resource (SkillGild session) and states the scope of what stops working afterward. Combined with the name skillgild_end_session, an agent can immediately distinguish it from start_session and the call/run/search siblings.
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?
It gives a clear trigger condition: 'when the task is done.' The paired sibling skillgild_start_session establishes the lifecycle implicitly. However, it does not address edge cases such as ending an already-ended session or when not to end one.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.