claude-session-continuity-mcp

Does 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. It does this well by detailing side effects ('inserts into the memories table and asynchronously generates a vector embedding'), knowledge graph behavior ('If relatedTo is provided, also creates a knowledge graph edge'), and return value ('Returns the new memory ID'). However, it doesn't mention error conditions, rate limits, or authentication requirements.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by important behavioral details and usage guidance. Every sentence earns its place by providing distinct value, though it could be slightly more streamlined by combining some concepts.

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 creation tool with no annotations and no output schema, the description provides good completeness: it explains the creation process, side effects, return value, and usage guidance. The main gap is lack of error handling information, but otherwise it covers the essential context needed to understand this tool's behavior and proper use.

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 schema already documents all parameters thoroughly. The description doesn't add significant meaning beyond what's in the schema properties - it mentions memory types and tags but these are already covered in the enum and array descriptions. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 tool's purpose with specific verbs ('store a piece of knowledge') and resource ('memory system'), distinguishing it from siblings like memory_search (for retrieval) and memory_get (for fetching specific memories). It explicitly identifies what gets created (memories with types, tags, embeddings) and the system involved.

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 explicit guidance on when to use this tool vs. alternatives: it instructs to 'use memory_search to verify no duplicate exists before storing,' directly naming a sibling tool and specifying a prerequisite action. This creates clear context for usage relative to other memory-related tools.

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