merge_people

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It clearly labels the operation as 'DESTRUCTIVE and IRREVERSIBLE' and explains that merged persons are permanently deleted with faces transferred. It could mention if the operation is atomic or logged, but the core warning is sufficient.

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 concise, with no unnecessary words. It presents purpose first, then guidelines, then parameter details in a clear, structured manner. Every sentence adds value.

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 2 parameters, no annotations, and no output schema details, the description covers all necessary context: when to use, what happens to data, and what each parameter does. It is complete for an agent to select and invoke the tool 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?

Schema description coverage is 0%, so the description must explain parameters. It does so thoroughly: person_id as 'target person UUID to keep' and merge_ids as 'List of person UUIDs to absorb into the target' with their behavioral effects (permanently deleted). The description adds essential context beyond the 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 clearly states the action 'Merge multiple person clusters into one' and specifies the precise use case: when the same real person has been split into multiple face clusters. This distinguishes it from sibling tools like reassign_face or update_person.

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 explicitly says when to use this tool ('Use this when the same real person has been split into multiple face clusters') and warns about destructiveness, providing clear context. It does not explicitly state when not to use, but the purpose is narrow enough that it's clear.

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