Memory MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'preserving previous observations' which adds useful context about data retention, but doesn't cover other critical aspects: whether this requires specific permissions, if updates are reversible, what happens to metadata not mentioned, error conditions, or response format. For a mutation tool with zero annotation coverage, this is insufficient.

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 extremely concise - a single sentence that efficiently communicates the core action and a key behavioral constraint. Every word earns its place with no redundancy or unnecessary elaboration. It's front-loaded with the primary purpose.

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 mutation tool with 3 parameters, no annotations, and no output schema, the description is incomplete. While concise, it lacks critical information about permissions, error handling, response format, and detailed behavioral expectations. The 'preserving previous observations' hint is helpful but insufficient for a tool that modifies data with multiple optional parameters.

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?

Schema description coverage is 100%, so the schema already documents all three parameters (metadata, name, observations) with their types and optionality. The description adds minimal value beyond the schema - it implies observations are preserved rather than replaced, but doesn't clarify parameter interactions or provide format examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Update' and resource 'entity', specifying it updates an existing entity. It distinguishes from sibling 'create_entities' by focusing on updates rather than creation, but doesn't explicitly differentiate from other update-like tools like 'add_observations' or 'delete_entities'.

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 no guidance on when to use this tool versus alternatives. It mentions 'preserving previous observations' which hints at behavior but doesn't specify when to choose this over 'add_observations' for observation management or 'create_entities' for new entities. No explicit when/when-not rules or prerequisites are provided.

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