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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the agent already knows this mutates/queues against an open-world system. The description adds genuinely useful behavior beyond that: it is a queued async task ('Queue a LinkedIn Unibox sync'), returns taskId/taskIds, and the task result reports chatResync. Missing only detail on failure/timeout behavior.

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 leading bracket boilerplate '[Ids in: … Ids out: …]' is awkward, machine-like noise that precedes the actual purpose sentence, hurting front-loading. The remaining two sentences are dense but earn their place describing resync behavior and task output.

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 3-param async queue tool with no output schema, the description covers the key unknowns: it queues a task, emits taskId/taskIds, and reports chatResync in the result. Combined with full schema coverage for all three parameters, an agent has enough to invoke it correctly; only error/rate-limit behavior is absent.

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 the schema already documents threadOnly, conversationUrl, and linkedinConnectionId in detail. The description's '[Ids in: …]' block largely restates the schema (conversationUrl meaning) and adds no syntax or format detail. Baseline 3 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 states a specific verb and resource – 'Queue a LinkedIn Unibox sync for the active setup, or fetch one conversation thread' – and the second sentence explains a concrete resync capability. However, it does not distinguish itself from closely related siblings like resync_chat, resync_attendee_chats, get_conversation, or list_conversations, so an agent still has to guess why this tool rather than those.

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 implied usage context: threadOnly with a conversationUrl fetches a single thread, and a profile URL on a live-session sender triggers a re-sync. But the description never states when to prefer sync_inbox over the sibling resync_chat or get_conversation, nor any exclusions or prerequisites like account state, leaving routing to inference.

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