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. It fails to disclose any behavioral traits such as what the tool returns, whether it has side effects, or how it influences the agent's workflow. The description is minimal and does not add meaningful context beyond the vague purpose.

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, concise sentence that is front-loaded with the main instruction. It avoids redundancy and is appropriately sized for a tool with no parameters, though it could be slightly more informative without losing efficiency.

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 (low, with 0 params) but lack of annotations and output schema, the description is incomplete. It does not explain what happens after calling the tool (e.g., does it return a status, trigger an action, or provide feedback?), leaving significant gaps in understanding its role in the workflow.

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 schema description coverage is 100%, so there is no need for parameter details in the description. The baseline for 0 parameters is 4, as the description does not need to compensate for missing param info, and it appropriately avoids unnecessary parameter discussion.

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 the tool should be called 'whenever you feel that you are done with what the user has asked for,' which is a tautology of the tool name 'think_about_whether_you_are_done.' It does not specify what the tool actually does (e.g., triggers a completion check, logs status, or returns a decision). The purpose is vague and lacks a clear verb+resource distinction.

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 implied usage by stating 'whenever you feel that you are done,' which gives some context for when to call it. However, it does not explicitly differentiate from sibling tools (e.g., 'think_about_collected_information' or 'think_about_task_adherence') or specify alternatives, leaving gaps in guidance.

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