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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, and the description adds behavior beyond that: this queues an asynchronous task, may re-sync from LinkedIn at fetch time on a live-session sender, and the task result carries a 'chatResync' field. No contradiction, though polling via get_unibox_task_status is never mentioned.

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, front-loaded with the primary queue action before the conditional thread resync path. The second sentence is dense and relies on jargon ('chatResync', 'live-session sender'), but every clause carries information rather than padding.

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 zero-required-parameter, three-parameter tool with no output schema, the description covers both execution modes, the triggering condition for the threadOnly path, and where the result surfaces. Only the async follow-up (that progress is checked via get_unibox_task_status) is left implicit.

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 threadOnly, conversationUrl, and linkedinConnectionId are fully documented in the schema; baseline is 3. The description reinforces the threadOnly + profile-URL combination but adds no syntax or format detail beyond what the schema already states.

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 uses a specific verb+resource ('Queue a LinkedIn Unibox sync for the active setup') and separates the second mode ('or fetch one conversation thread'), so an agent can distinguish the sync action from read-only siblings like get_unibox or get_conversation. It stops short of naming any sibling explicitly, so differentiation is inferential rather than explicit.

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?

It gives concrete usage context for the threadOnly branch — a conversation the tool 'can't see yet' on a live-session sender, e.g. an older Sales Navigator InMail on a re-added account — which is exactly the situation that selects that mode. There are no exclusions or named alternatives (e.g. when to prefer a plain read), which keeps it below a 5.

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