Find duplicate Twenty CRM records

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

Annotations already declare readOnlyHint=true, destructiveHint=false. The description adds 'without modifying CRM data' which is redundant and does not clarify behavior like what happens if duplicates are found (return type, format, pagination). No new insights beyond annotations.

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 short (one sentence), which is generally good, but it lacks essential details that could be added without becoming verbose. It is not optimally structured for agent comprehension.

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 no output schema, no parameters, and a description that implies inputs, the tool definition is critically incomplete. There is no way for an AI agent to know how to invoke this tool correctly (e.g., what to pass, what to expect). Other sibling tools have richer descriptions.

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?

Input schema has zero parameters, yet the description mentions 'supplied record IDs or candidate data'. This is a direct contradiction. The description does not add meaning; it misleads about required inputs. Schema coverage is 100% (trivially) but description compensates negatively.

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 states the tool finds duplicates and is read-only, but it doesn't specify what constitutes duplicates (exact IDs vs fuzzy matching) or the scope (within a specific object type?). It moderately distinguishes from siblings like 'twenty_search_records' but not clearly.

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?

No guidance on when to use this tool versus other record tools (e.g., list, search, merge). The description says 'check supplied record IDs or candidate data' but the input schema has no parameters, creating confusion about how to supply data.

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