Stop a session's AGY process and keep it resumable, or set forget=True to delete its registry entry and scratch, backup, and log files.
Stop a session's AGY process. The session stays resumable unless forget=True, which also deletes it from the registry and removes its scratch, backup and log files.
| Name | Required | Description | Default |
|---|---|---|---|
| forget | No | ||
| session_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 burden and does it well: it discloses that stopping is non-destructive by default because the session remains resumable, and that forget=True is destructive, deleting the registry entry plus scratch, backup and log files. It omits idempotency and any error behavior for a session with no active process.
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 sentences, front-loaded with the core action and followed by the conditional exception. Every clause adds information; nothing is redundant with the name or title.
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?
An output schema exists, so return values need not be described. For a two-parameter lifecycle tool with a destructive flag, the description covers the main behavioral risk and the default safety profile; only edge-case behavior (no running process, already-ended session) is unaddressed.
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 coverage is 0%, so the description must supply parameter meaning, and it does for the risky one: forget=True is defined by its concrete side effects (registry deletion, file removal) rather than just 'forget the session'. session_id is left undefined, though its meaning is self-evident from the schema.
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 and resource ('Stop a session's AGY process') that an agent can map directly onto a session. It is distinguishable from agy_start and agy_resume via the resumability clause, though it never names those siblings explicitly.
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?
Use is implied: call it to stop a running session, and resumability is noted, which hints at agy_resume as the follow-up. There is no explicit when-not guidance, no stated alternative tool name, and no mention of what to do if no process is running.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.