Preview or merge Twenty CRM records

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

Annotations already mark destructiveHint=true; the description adds that TWENTY_ALLOW_DESTRUCTIVE must be set for actual merge, providing critical behavioral context beyond annotations. No contradiction.

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?

Two sentences, no wasted words. Every sentence earns its place by conveying default behavior and required conditions.

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 is minimal given the destructive and complex nature. It lacks details on what merging entails, impact on records, preview behavior, and return values. Annotations provide some context, but more completeness would be beneficial.

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 input schema is empty, so description must compensate. It effectively specifies required implicit parameters (dry_run, TWENTY_ALLOW_DESTRUCTIVE) that are not in the schema, adding essential meaning for invoking the tool correctly.

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 that the tool previews or merges records, with a default preview mode. It distinguishes itself from sibling tools like create/update by specifying the merge action, but does not explicitly differentiate from 'twenty_find_duplicates' which may be related.

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 clear guidance: preview by default, actual merge requires dry_run=false and TWENTY_ALLOW_DESTRUCTIVE=true. It does not specify when not to use or list alternatives, but the context is sufficient for correct invocation.

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