Deduplicate Neo4j Knowledge Graph Entities

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

Annotations already signal that this is a non-readonly, idempotent, non-destructive operation. The description adds the contextual detail that it operates on a namespaced Neo4j endpoint for a RAG system, but it doesn't explain side effects or merge behavior. This adds some value beyond annotations without contradicting them.

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, focused sentence with no redundant content. It front-loads the action and resource, making it easy to scan.

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?

The tool has a simple signature and annotations, but the description is minimal. It omits when to use it, what result to expect, and any caution about long-running or side effects. It is minimally viable but lacks richer context.

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 coverage is 100% and the single parameter 'rag_id' is already described as 'The ID of the RAG system'. The description's mention of 'namespaced endpoint' aligns with the parameter but doesn't add material new meaning beyond the schema.

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 uses a specific verb ('Deduplicate') and resource ('entities in the Neo4j knowledge graph'), clearly indicating the operation. It adds 'for a RAG system (namespaced endpoint)' which hints at the context and distinguishes it from the sibling lyzr_kg_deduplicate, though not explicitly naming alternatives.

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 like lyzr_kg_deduplicate or other KG tools. It lacks any 'when to use' or 'when not to use' instructions.

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