continue_conversation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Continue' implies a stateful interaction, but the description doesn't reveal what 'continue' does—whether it sends a message, updates a session, triggers analysis, or returns data. It lacks details on permissions, side effects, or response format, leaving significant gaps for an agent to understand the tool's behavior.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action, though it could be more informative. The brevity is appropriate but borders on under-specification given the tool's complexity.

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 likely complexity (involving ongoing conversations with parameters like session_id and message), no annotations, and no output schema, the description is incomplete. It doesn't explain what 'continue' means in practice, what the tool returns, or how it fits into the broader conversation workflow, making it inadequate for an agent to use effectively.

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 fully documents the three parameters (session_id, message, include_code_snippets). The description adds no meaning beyond this, such as explaining how parameters interact (e.g., 'message' is Claude's input to continue the conversation) or providing usage examples. Baseline 3 is appropriate when 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 'Continue an ongoing analysis conversation' states a verb ('Continue') and resource ('ongoing analysis conversation'), providing a basic purpose. However, it's vague about what 'continue' entails operationally and doesn't distinguish this tool from sibling tools like 'get_conversation_status' or 'finalize_conversation', which also relate to conversation management.

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 offers no guidance on when to use this tool versus alternatives. It doesn't specify prerequisites (e.g., requires an existing session started with 'start_conversation'), exclusions, or contextual cues for choosing it over other conversation-related tools in the sibling list.

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