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 discloses behavioral traits like using markdown formatting, keeping content short, and preferring multiple small memories over large ones. However, it doesn't cover important aspects like whether this is a destructive operation (though implied by 'write'), error conditions, or what happens on success/failure.

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 appropriately sized and front-loaded with the core purpose. However, it includes some redundancy (e.g., explaining why multiple small memories are better could be more concise) and the final sentence about usage scenarios could be integrated more smoothly.

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 no annotations, no output schema, and 3 parameters with 0% schema coverage, the description provides reasonable context for a write operation but has significant gaps. It covers purpose and usage guidelines well, but lacks details about return values, error handling, and complete parameter documentation, making it incomplete for reliable tool invocation.

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?

With 0% schema description coverage and 3 parameters, the description adds minimal semantic value. It mentions 'memory_name' should be meaningful and 'content' should use markdown, but doesn't explain 'max_answer_chars' at all. The description doesn't adequately compensate for the schema's lack of parameter documentation.

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: 'Write some information about this project that can be useful for future tasks to a memory.' It specifies the verb ('write'), resource ('memory'), and content type ('information about this project'), though it doesn't explicitly differentiate from sibling tools like 'read_memory' or 'delete_memory' beyond the obvious action difference.

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: 'This tool is either called during the onboarding process or when you have identified something worth remembering about the project from the past conversation.' It clearly defines two specific scenarios for usage, though it doesn't mention alternatives or exclusions.

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