merge_customers

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

Description explicitly states that merged records are deleted and returns {success}, adding behavioral context beyond the annotation's destructiveHint=true. However, it does not mention side effects like handling of associated data or rollback.

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?

Single sentence conveys purpose, key behavior (deletion), and return value. No wasted words; front-loaded with essential information.

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?

With two well-documented parameters, destructive annotation, and simple return, the description is mostly complete. It lacks details about conflict resolution or handling of related records, but these are edge cases.

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?

Schema coverage is 100% with clear descriptions for both parameters. The description adds no additional parameter-level meaning, so baseline score of 3 applies.

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?

Description clearly states the action ('merge duplicate customers'), the resource ('customers'), and key outcomes (target kept, merged deleted). This distinguishes it from other customer tools like create_customer, update_customer, etc.

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?

Description implies usage when duplicates exist but does not explicitly state when to use this tool versus alternatives (e.g., update_customer) or conditions/limitations. No guidance on when not to use.

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