priority_dedup

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

No annotations exist, so the description carries full burden. It discloses the deduplication algorithm and dryRun support, but omits critical details such as whether the tool is destructive, what happens to relations, and what the return value is beyond dryRun.

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?

A single, well-structured sentence that front-loads the purpose and efficiently conveys the priority hierarchy without wasted words.

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 description lacks details on return value (no output schema), side effects, and interaction with entities/relations. Given the tool's complexity and lack of output schema, it should explain what the tool returns or how changes are applied.

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% with a clear description for the single parameter `dryRun`. The tool description adds the algorithm context but does not enhance parameter semantics beyond the schema already provided.

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 it performs 'priority-based deduplication' and specifies the priority order (importance > recency > observation count > tags), distinguishing it from sibling tools like 'find_duplicates' or 'merge_entities' that either only identify duplicates or merge without priority scoring.

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 implies the tool is for priority-based deduplication but does not explicitly state when not to use it or suggest alternatives. It provides clear context for usage with the algorithm details, but lacks explicit guidance compared to other tools.

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