find_duplicates

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 mentions 'potential duplicate entities' and 'similarity', but doesn't disclose critical behavioral traits like what constitutes a duplicate, how similarity is calculated, whether this is a read-only operation, what permissions are needed, or what the output looks like. For a tool with no annotation coverage, this leaves significant gaps.

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 wasted words. It's appropriately sized for a simple tool and front-loads the core purpose immediately.

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 duplicate detection (which often involves algorithms, confidence scores, and result formats), no annotations, no output schema, and many sibling tools, the description is incomplete. It doesn't explain what 'potential' means, how results are returned, or provide enough context for an agent to use it effectively compared to alternatives.

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?

The description adds no parameter-specific information beyond what's in the schema. With 100% schema description coverage (the 'threshold' parameter is fully documented in the schema), the baseline score is 3. The description doesn't compensate with additional context about how the threshold affects results or typical usage values.

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 'Find potential duplicate entities based on similarity' clearly states the tool's purpose with a specific verb ('Find') and resource ('duplicate entities'), but it doesn't differentiate from sibling tools like 'find_similar_entities' or 'fuzzy_search'. The purpose is understandable but lacks sibling distinction.

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. With many sibling search-related tools (e.g., 'find_similar_entities', 'fuzzy_search', 'semantic_search'), there's no indication of when this specific duplicate-finding tool is appropriate or what makes it unique.

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