merge_contact_profiles

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

The description notes the tool is mutating and explains the dryRun parameter's role ('Set dryRun=false to merge'), adding behavioral context beyond annotations. Annotations indicate readOnlyHint=false and destructiveHint=false, which are consistent with the description. The description also mentions combining contact IDs, which is useful but could elaborate on reversibility or permissions.

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 three sentences with no wasted words. It starts with the core action, explains the effect, provides usage guidance, and ends with a key behavioral note. All sentences contribute meaningfully.

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?

For a mutation tool with no output schema, the description adequately explains the merge operation and dryRun behavior. It could be improved by noting potential errors (e.g., if profiles don't exist) or prerequisites, but overall it is sufficiently complete given the annotations and 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?

With 100% schema coverage, the baseline is 3, but the description adds value by explaining the direction of merging ('source profile data is merged into the target') and the significance of dryRun. This clarifies parameter roles beyond the schema descriptions.

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 the tool merges two contact profiles into one, specifying the source and target. It uses the verb 'Merges' and identifies the resource as 'Cognigy.AI contact profiles'. The description also distinguishes from siblings like 'unmerge_contact_profiles' and 'remove_contact_id' by implying it combines profiles.

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 a clear use case: 'Use when the same user has multiple profiles.' This is explicit guidance on when to apply the tool. However, it does not mention when not to use it or name alternative tools, though siblings like 'unmerge_contact_profiles' exist.

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