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. While it mentions this is a deletion operation (implying destructive action), it doesn't specify whether the deletion is permanent/reversible, what permissions are required, or what happens if the file doesn't exist. For a destructive operation 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 efficiently structured in two sentences: the first states the core action, the second provides crucial usage guidelines. Every sentence adds value with zero wasted words, making it easy to parse and understand quickly.

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?

For a destructive operation with no annotations and no output schema, the description provides good usage guidelines but lacks critical behavioral details (permanence, error handling, permissions). The single parameter is undocumented. While the purpose and usage are clear, the description doesn't fully compensate for the missing structured information.

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 schema has 0% description coverage for its single parameter 'memory_file_name'. The description doesn't mention this parameter at all, providing no additional semantic context beyond what the schema's title suggests. However, with only one parameter, the baseline is 4, but the complete lack of parameter explanation in the description reduces this to 3.

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 verb 'delete' and the resource 'memory file', making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'remove_project' or 'delete_lines', which might also involve deletion operations.

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 guidance on when to use this tool: 'only if a user asks for it explicitly' and gives concrete examples ('information retrieved... no longer correct or no longer relevant'). This clearly defines the triggering conditions and helps distinguish it from other deletion tools.

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