find_duplicate_groups

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

No annotations are provided, so the description carries full burden. It describes the grouping action but lacks details on edge cases (e.g., empty list, duplicate values), performance considerations, or how scoring works internally. The brief parameter explanations do not cover behavioral nuances.

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 efficiently structured with a clear lead sentence, bullet-point use cases, and a labeled parameter list. It avoids unnecessary words and front-loads the core purpose, making it scannable for an agent.

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 tool's moderate complexity (4 parameters, 2 enums, output schema present), the description covers purpose and basic parameter semantics. However, it omits expected output format (though output schema exists), behavioral constraints, and more detailed usage context relative to siblings, leaving room for improvement.

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 0%, so the description must compensate. It provides short explanations for each parameter (e.g., threshold: 'Minimum score for joining a group'), adding meaning beyond the schema's names and types. However, explanations are minimal and do not elaborate on how values affect behavior, leaving gaps.

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 'Group strings that probably represent the same entity,' which is a specific verb and resource. It lists concrete use cases like company-name deduplication and customer-name cleanup, distinguishing it from sibling tools like compare_strings or find_best_matches that focus on comparison or single match retrieval.

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 explicit 'Useful for' scenarios, giving context on when to use the tool. However, it does not discuss when not to use it or contrast with alternatives like compare_strings for pairwise comparison or explain_match for explanation, limiting guidance for an agent.

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