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 effectively describes key traits: it's read-only (safety profile), returns an array of task objects with specific fields and a summary count, and has a default filter ('pending') with an option to see all. It covers output format and default behavior, though it lacks details on error handling or pagination.

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 front-loaded with the core purpose, followed by return details and behavioral notes in two efficient sentences. Every sentence adds value: the first defines the action and filter, the second specifies output and defaults. No wasted words, making it highly concise and well-structured.

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 moderate complexity (2 parameters, no output schema, no annotations), the description is largely complete. It covers purpose, usage, behavior, and output format adequately. However, it lacks details on error cases (e.g., invalid project name) or performance aspects like pagination, which could be helpful for an agent.

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 description coverage is 100%, so the schema already documents both parameters (project and status) with descriptions and enum values. The description adds minimal value beyond the schema by mentioning the default filter ('pending') and the effect of status='all', but this is largely redundant with the schema's enum and default note. Baseline 3 is appropriate as 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 specific action ('List tasks for a project, filtered by status'), distinguishes it from siblings like task_add or task_update by specifying it's read-only, and identifies the resource (tasks) with filtering scope. It goes beyond a tautology by detailing the return format and default behavior.

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 list tasks with status filtering) and implicitly distinguishes it from siblings like list_projects (which lists projects, not tasks) or task_suggest (which suggests tasks). However, it does not explicitly state when not to use it or name alternatives, such as for adding or updating tasks.

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