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

Goes well beyond the annotations: discloses merge-not-replace semantics, the irreversibility of the operation (no delete tool), and a recommended pre-check. Annotations (destructiveHint=false, idempotentHint=false) are consistent with an additive, non-undoable write, and the description supplies the practical consequence the flags don't convey.

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?

Two sentences, zero waste: the core action comes first, then the merge semantics, then the prerequisite. The parenthetical caveat about no removal tool is placed exactly where it matters.

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 2-param mutation with no output schema, the description covers what changes, what does not change (destination rules preserved), that the change cannot be undone, and how to preview the outcome. Nothing an agent needs before calling is missing.

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% and the schema already labels `linkedAccountId` as source and `newLinkedAccountId` as destination. The description's 'from one account onto another' mirrors that mapping without adding new detail such as ID format or validation.

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+resource+scope: cloning every exclusion rule from one LinkedIn account to another. Clearly distinguishes itself from siblings like blacklist_add (single rule), blacklist_list (read), and blacklist_delete by making it a whole-set transfer between two accounts.

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?

Explicitly routes the agent through a prerequisite: read the destination with `blacklist_list` first. It also gives a negative constraint (no removal tool exists afterwards), which is exactly the when-to-be-careful guidance an agent needs.

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