contact_merge

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

The description is too minimal to disclose behavioral traits. However, the input schema's parameter descriptions partly compensate by stating that the mergee contact will be deleted. With no annotations, the description could have added more safety context.

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 extremely concise at two words, with no wasted text. However, it sacrifices clarity for brevity.

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?

Given the destructive nature of the operation (one contact deleted), the description lacks essential context about return values, error handling, and when to avoid use. No output schema or annotations exist to compensate.

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%, and the schema already describes both parameters fully. The description adds no extra meaning beyond the schema, meeting the baseline but not contributing additional value.

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 'Merge Contacts' is a clear verb+noun indicating the action and resource. It distinguishes from sibling tools like contact_update and contact_delete, but lacks specificity about the merge outcome.

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?

No guidance on when to use this tool versus alternatives such as contact_update or contact_delete. The description does not provide context for when merging is appropriate.

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