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' (safety profile), 'Returns an array of project summary objects' (output format), and 'No parameters required' (invocation simplicity). It doesn't mention rate limits, authentication needs, or pagination behavior, but covers the essential operational characteristics.

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 perfectly front-loaded with the core purpose, followed by key details (metadata returned, read-only nature, return format, parameter information). Every sentence earns its place with zero wasted words, and the structure flows logically from what to why to how.

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 zero-parameter read-only tool with no output schema, the description provides excellent coverage: purpose, scope, returned metadata, safety profile, return format, and invocation details. The only minor gap is not explicitly describing the structure of 'project summary objects' in the returned array, but given the tool's simplicity and lack of output schema, this is reasonable.

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 schema has 0 parameters with 100% coverage, so the description's statement 'No parameters required' perfectly aligns with the schema. While there are no parameters to document, the description provides useful context about what the tool examines (projects under apps/ directory) which adds semantic value beyond the empty 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?

The description clearly states the verb ('List') and resource ('projects under the apps/ directory'), specifies the scope ('all projects'), and distinguishes from siblings by focusing on directory listing rather than analysis, initialization, or status checking. It explicitly mentions what information is returned (platform type, initialization status, session context existence).

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: to get a comprehensive list of projects in the apps directory with specific metadata. It doesn't explicitly state when not to use it or name alternatives, but the context implies this is for directory overview rather than detailed analysis (project_analyze) or status checking (project_status).

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