claude-session-continuity-mcp

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

With no annotations provided, the description carries full burden and does well by disclosing key behaviors: side effects ('writes to SQLite'), auto-detection capability, idempotency, and that it updates existing records. It doesn't mention authentication needs or rate limits, but covers most critical operational aspects.

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?

Front-loaded with the core purpose, followed by important behavioral details and usage guidance. Every sentence adds value: creation details, auto-detection, side effects, idempotency, and when to call. No wasted words.

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 tool with no annotations and no output schema, the description provides good coverage of what the tool does, when to use it, and key behaviors. It could mention what happens on failure or provide more detail about the update behavior, but overall it's quite complete given the context.

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%, so the baseline is 3. The description adds some context about tech stack auto-detection from specific files and that the 'techStack' parameter is an override, but doesn't provide additional semantic meaning beyond what the schema already documents.

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 specific action ('Initialize a new project'), the system ('continuity system'), and the resources affected ('project_context and active_context tables'). It distinguishes this from sibling tools like 'session_start' by specifying this is for initial setup only.

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?

Explicitly states when to use ('Call this once when adding a new project') and when not to use ('then use session_start for subsequent sessions'). It also provides context about idempotency, making it safe for already-initialized projects.

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