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 explicitly states 'Read-only,' which is crucial for safety, and describes the scope of data returned (aggregate stats, breakdowns, top/recent entries). It could improve by mentioning potential performance impacts or data freshness, but it adequately covers key behavioral traits for a read-only diagnostic tool.

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 efficiently structured: it front-loads the core functionality, lists specific statistics, states behavioral traits, provides usage context, and notes the optional parameter—all in three concise sentences with zero wasted words. Every sentence adds essential information.

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?

Given the tool's complexity (aggregate statistics with multiple breakdowns), lack of annotations, and no output schema, the description does a good job of explaining what the tool returns. However, it could be more complete by specifying the format of the statistics (e.g., numerical counts, percentages) or any limitations (e.g., time ranges for 'recent entries'), which would help the agent interpret results without an output schema.

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?

The input schema has 100% description coverage, with the single optional parameter 'project' clearly documented in the schema. The description adds marginal value by reiterating the optional scoping to a single project, but does not provide additional semantics beyond what the schema already states. This meets the baseline for high schema coverage.

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 ('Get aggregate statistics') and resource ('memory system'), with detailed enumeration of what statistics are included (total count, breakdowns by type/project, top accessed, recent entries). It distinguishes itself from siblings like memory_get, memory_search, or memory_store by focusing on aggregate metrics rather than individual memory operations.

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 clear context for when to use this tool ('Useful for understanding memory distribution and system health') and includes an optional scoping parameter for a single project. However, it does not explicitly state when not to use it or name specific alternatives among siblings (e.g., project_status or memory_search might overlap in some contexts).

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