Continue Claude Session

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It discloses that incorrect workspace_dir causes session not found, and that answering questions unblocks better conclusions. However, does not mention side effects, session lifetime, or what the response looks like. Adequate but not rich.

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?

Three sentences, each provides necessary information without redundancy. Front-loaded with primary purpose, then key constraints, then special use case. No wasted words.

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?

Handles core usage well: how to continue session and handle questions. No output schema, so description could elaborate on expected return, but for a continuation tool the behavior is fairly straightforward. Misses guidance on session persistence or error cases beyond workspace mismatch.

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 coverage is 100% with descriptions, so baseline 3. Description adds context: explains the relationship between session_id and workspace_dir, and the purpose of answering questions. For model and stance, it doesn't elaborate beyond schema, but overall adds value.

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?

Clearly states it continues an existing Claude conversation, distinguishing it from siblings like ask_claude (starts new), claude_debate_* (debates), and claude_review_* (reviews). The verb 'continue' plus resource 'session' is specific.

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?

Provides explicit when-to-use: when you have a session_id and follow-up message. Mentions workspace_dir must match original, otherwise session not found. Also advises using this tool to answer questions from previous response. Lacks explicit 'do not use if' scenarios but is clear enough.

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