Context Continuation MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. 'End' implies a destructive/mutative operation that terminates session state, but the description doesn't specify whether this is reversible, what data is preserved/lost, or if authentication/permissions are required. It mentions an optional summary parameter but doesn't explain its purpose or effect.

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource. Every word earns its place - 'End' specifies the action, 'the current context tracking session' specifies exactly what's affected.

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 session termination tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'ending' entails (data persistence, cleanup, notifications), what happens to tracked messages/decisions/milestones, return values, or error conditions. Given the sibling tools suggest a rich context tracking system, this description leaves too many behavioral questions unanswered.

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% (the single parameter 'summary' is documented in schema as 'Optional session summary'), so the baseline is 3. The description doesn't add any parameter information beyond what the schema provides - it doesn't explain what constitutes a useful summary, format expectations, or how the summary is used after session termination.

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 clearly states the action ('End') and resource ('current context tracking session'), making the purpose immediately understandable. It distinguishes from siblings like 'context_start_session' by specifying the opposite operation. However, it doesn't explicitly differentiate from 'context_restore_session' which might also involve session state changes.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., must have an active session started with 'context_start_session'), when not to use it, or what happens if called without an active session. The sibling tools include session management alternatives, but no comparison is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.