pipedrive_organizations_merge

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

With no annotations, the description carries the full behavioral burden and does disclose two important traits: a confirm token guard ('MERGE') and dry_run support. However, it stops short of stating that the operation is irreversible or that the source org is destroyed/its deals and persons reassigned, leaving the key destructive consequence to the schema's parameter text.

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?

Four short, front-loaded sentences with no filler; the directional rule and guard requirement come early. It is telegraphic rather than wasteful, though it could be slightly more fluent.

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 destructive, annotation-free operation with no output schema, the description covers direction, the confirmation gate, and dry_run, which is adequate. It still omits irreversibility and side effects on related entities, which an agent should know before committing a merge.

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 100%, so all four parameters are already documented in the schema, including the confirm const value and the source/target directionality. The description's mention of confirm:'MERGE' and dry_run simply echoes structured data without adding syntax or constraints, so the baseline 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?

States a specific verb (merge) and resource (organizations) and clarifies the direction of the operation with 'Source is merged into target'. It is distinguishable from pipedrive_organizations_delete, though it does not explicitly contrast itself with the parallel pipedrive_persons_merge sibling.

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 gives no when-to-use guidance, no prerequisites, and does not mention alternatives such as delete or update. A reader must infer that this is for consolidating duplicate organizations from the name alone.

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