Enhanced Knowledge Graph Memory 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 of behavioral disclosure. 'Merge multiple entities into one' implies a destructive mutation (entities are combined, possibly altering or deleting original data), but it doesn't specify critical details: whether the merge is reversible, what happens to properties/relations of merged entities, if permissions are required, or the output format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence with zero waste: 'Merge multiple entities into one'. It is front-loaded and directly conveys the core action without unnecessary elaboration. Every word earns its place, making it easy for an agent to parse 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?

Given the complexity of a merge operation (likely destructive), lack of annotations, and no output schema, the description is incomplete. It doesn't explain the merge behavior (e.g., how conflicts are resolved), prerequisites, or what is returned. For a tool that could significantly alter data, more context is needed to ensure safe and correct usage by an agent.

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%, with clear descriptions for 'entityNames' ('Entities to merge') and 'targetName' ('Optional target entity name'). The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints (e.g., minimum number of entities). With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't detract either.

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 'Merge multiple entities into one' clearly states the verb ('merge') and resource ('entities'), specifying the action and target. It distinguishes from siblings like 'create_entities' or 'delete_entities' by focusing on consolidation rather than creation or removal. However, it doesn't specify what 'entities' are in this context (e.g., nodes in a graph) or how the merge operation works, which prevents a perfect score.

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 doesn't mention prerequisites (e.g., existing entities to merge), exclusions (e.g., cannot merge entities with conflicting properties), or comparisons to siblings like 'merge_tags' or 'find_duplicates'. Without such context, an agent must infer usage from the tool name alone.

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