deals_merge

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

Discloses all critical behaviors: source deletion, transfer of activities/notes/followers, merging of products/files/participants, and irreversibility. No annotations were provided, so the description fully covers the tool's impact.

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?

Well-organized with clear sections (description, workflow tips, common use cases, warning). Every sentence adds value without redundancy. Front-loads key information about deletion and target preservation.

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?

Thoroughly covers all relevant aspects: purpose, parameter roles, data transfer details, irreversibility, and examples. No gaps remain given the tool's complexity and lack of output schema.

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 already describes each parameter well (100% coverage). The description adds context by clarifying the roles of source and target, providing examples, and explaining consequences beyond schema details.

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 it merges two deals, specifying which deal is deleted and which is kept. It distinguishes itself from sibling tools like deals_delete or deals_update by focusing on merging and data combination.

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?

Explicit guidance on when to use (e.g., duplicate cleanup), which ID is source vs target, and workflow tips like reviewing deals before merging. Includes common use cases and clear warnings about irreversibility.

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