resolve_duplicate_users

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It indicates a destructive write operation (merging and removing users) but lacks details on reversibility, side effects, or constraints beyond the token requirement.

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 with two sentences: the first states the core functionality, the second a critical requirement. No wasted words or redundancy.

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 lack of annotations and output schema, the description is somewhat minimal. It covers the basic operation and a requirement, but omits potential edge cases, return format, and error conditions that would be helpful for a destructive merge tool.

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 clear descriptions for both parameters ('User id to keep' and 'User ids to merge into primary_id and remove'), so the description adds no additional semantic value beyond confirming the merge action.

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's action: 'Merge duplicate_ids into primary_id, keeping primary_id as the surviving user.' It uses a specific verb and resource, and is distinct from sibling tools which handle enable/disable, listing, and role management.

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 mentions the prerequisite 'Requires SYSTEM token' but does not explicitly state when to use this tool vs alternatives. The purpose is clear from context, but exclusion criteria or when-not-to-use guidance is missing.

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