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

With annotations only declaring destructive/openWorld/non-idempotent, the description carries substantial extra weight: ten-minute preview expiry, idempotency per receipt, the confirm:true gate, revision/connected_at conflict semantics, the verified:false fallback with no profile_url, and the exact blast radius of remove_history (messages and teammate access removed, published CRM notes retained). That is far more than the annotations 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?

The length is defensible for a ten-action state machine, and purpose plus the 'When to use' line are front-loaded. However, the middle is a single dense run-on paragraph covering all ten actions with no grouping or bullets, which makes the action/precondition mapping harder to scan than it needs to be.

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?

An output schema exists, so return values need not be described, and the annotations cover the safety profile. The description still supplies everything else an agent needs: action inventory, required confirmations, preview/receipt lifecycle, conflict detection, and privacy guardrails ('never infer consent from private message text').

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 coverage is 100%, so the baseline is 3, but the description adds cross-parameter workflow meaning the schema cannot express: which fields pair with which prepare/save step, that receipt replay is per-receipt idempotent, and that revisions must match what get_context displayed. It does not re-document individual field types, which is appropriate.

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 first sentence names the resource and scope precisely ('manage one of the user's own LinkedIn conversations'), and the body spells out the ten distinct actions (contact linking, sync on/off, teammate access, note publishing). It clarifies the boundary ('These controls never send LinkedIn messages'), though it never names a sibling such as add_note to distinguish note publishing from generic note tools.

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?

There is an explicit 'When to use' clause enumerating the four use cases, plus a concrete example, and the narrative dictates the ordering constraints (prepare_contact before save_contact, explicit confirmation before save). It stops short of naming an alternative tool to use instead when the conversation is not the right target.

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