profiles_merge

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Merge duplicate profiles' implies a mutation but does not state whether the merged profiles are deleted, whether the operation is reversible, or what permissions are required. This is a severe gap for a destructive merge operation.

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 only three words, which is exceedingly terse. While it is front-loaded, it is under-specified to the point of being unhelpful. It reads more like a label than a description, so it fails to earn its place as a complete description.

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 tool that performs a destructive merge operation with no annotations, the description is critically incomplete. It lacks any information about prerequisites, side effects, or behavior beyond the bare action. The presence of an output schema does not compensate for the missing operational context.

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 description coverage is 0%, and the description does not compensate. While parameter names like main_profile_id and profile_ids_to_merge are suggestive, the description doesn't explain their exact roles (e.g., whether the listed profiles are deleted after merging) or the purpose of domain_name. The short phrase adds minimal semantic value over the raw schema.

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 duplicate profiles' clearly identifies a merge operation on profiles, distinguishing it from sibling tools like profiles_update_profile and profiles_delete_profile. It is concise and uses a specific verb plus resource, but lacks detail on the relationship between main_profile_id and profile_ids_to_merge, so it isn't a perfect 5.

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no typical scenarios. It is a single phrase with zero context, so the agent is left without information about appropriate usage.

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