merge_customers

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

The description explicitly states that merged records are DELETED, which aligns with the destructiveHint=true annotation and adds behavioral specificity beyond the annotation. It also discloses the return shape as {success}, which is helpful given no output schema. It does not contradict 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 two sentences, front-loaded with the core action and key warning, and contains no redundant information. Every word earns its place.

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 simple merge operation, the description covers purpose, destructive behavior, and return type. The schema fully documents parameters. It could mention prerequisites or atomicity, but overall it is sufficiently complete for an agent to invoke correctly.

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 provides complete descriptions for both parameters (100% coverage), so the description adds minimal semantic value. The phrase 'merged records are DELETED' reinforces what happens to merged_customer_ids, but the schema already says 'will be deleted'.

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 action ('Merge duplicate customers into a target') and highlights the key destructive consequence ('merged records are DELETED'). It is specific about the resource and operation, making it easy to distinguish from customer creation, update, or retrieval tools.

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 gives clear context for when to use the tool: when there are duplicate customers to consolidate. It does not explicitly name alternative tools, but the purpose is evident given the sibling tool set (e.g., update_customer for single edits). This is clear context with no exclusions.

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