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 side effects ('inserts into the tasks table'), return value ('Returns the created task ID'), and persistence mechanism ('persisted in SQLite'). It doesn't mention authentication needs, rate limits, or error conditions, but covers core behavioral aspects adequately.

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 with three sentences that each earn their place: first states purpose and key features, second covers side effects and returns, third provides usage guidelines. No wasted words, well front-loaded with the core functionality.

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 coverage: purpose, behavioral traits (side effects, returns), usage guidelines, and persistence details. It doesn't explain error cases or the full return format beyond the ID, but given the schema completeness and clear purpose, it's reasonably complete.

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 5 parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it mentions 'priority ranking' and 'optional file associations' which align with the schema but don't provide additional meaning. Baseline 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 specific action ('Add a new task') and resource ('to a project's backlog'), distinguishing it from siblings like task_list (view), task_suggest (auto-generate), and task_update (modify). It provides concrete details about persistence (SQLite) and functionality (priority ranking, file associations).

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 explicitly provides when-to-use guidance: 'Use task_list to view existing tasks before adding duplicates' and 'Use task_suggest to auto-generate tasks from code comments (TODO/FIXME).' This clearly differentiates this tool from alternatives and prevents misuse.

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