Serena MCP Server

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 explains the tool's purpose (restarting), the triggering condition (outdated state from external edits), and the impact (resolving errors). However, it lacks details on side effects, such as whether the restart is disruptive or temporary.

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 concise and well-structured: it front-loads the primary usage rule, explains the rationale, and provides actionable guidance. Every sentence adds value without redundancy, making it efficient for an AI agent.

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 complexity (a restart operation with no parameters and no output schema) and lack of annotations, the description is mostly complete. It covers the purpose, usage rules, and context, but could benefit from mentioning potential side effects or confirmation details to be fully comprehensive.

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 with 100% schema description coverage, so no parameter documentation is needed. The description appropriately focuses on usage context without redundant parameter details, meeting the baseline for this scenario.

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 tool's purpose: restarting the language server when its state becomes outdated due to external edits, which helps resolve editing errors. It specifies the verb ('restart') and resource ('language server'), though it doesn't explicitly differentiate from sibling tools like 'activate_project' or 'switch_modes'.

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 explicit usage guidelines: use only on explicit user request or after confirmation, and suggest it when editing errors occur due to outdated language server state. It clearly defines when to use the tool, though it doesn't mention specific alternatives among siblings.

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