Serena MCP Server

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. The description mentions 'preparing for a new conversation' but doesn't explain what this entails behaviorally—whether it clears memory, resets state, requires specific permissions, has side effects, or what the expected outcome is. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 two short, clear sentences with zero wasted words. It front-loads the purpose and immediately follows with a critical usage guideline. Every sentence earns its place by providing essential information efficiently.

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 has 0 parameters, no annotations, and no output schema, the description provides basic purpose and strong usage guidelines but lacks details on what the preparation involves or what happens after invocation. For a tool that likely resets or initializes conversation state, more context on behavior and outcomes would be helpful, making it minimally adequate but with gaps.

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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics since there are none. Baseline for 0 parameters is 4, as the description appropriately doesn't discuss parameters and focuses on usage.

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 states 'Instructions for preparing for a new conversation' which is a tautology that essentially restates the tool name 'prepare_for_new_conversation'. It doesn't specify what the preparation actually involves (e.g., clearing context, resetting state, initializing settings) or what resource it operates on. The purpose remains vague rather than 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?

The description explicitly states 'This tool should only be called on explicit user request', providing clear guidance on when to use it (only when the user explicitly asks) and implying when not to use it (automatically or without user request). This is a strong, explicit usage rule that distinguishes it from alternatives.

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