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

Annotations declare readOnlyHint=false and openWorldHint=true, which could read as 'mutates LinkedIn', but the description explicitly resolves that with 'Nothing is sent or changed on LinkedIn.' The async start-then-poll behavior is a genuinely useful disclosure that annotations do not convey. It stops short of saying how long a sync takes or how to tell it finished.

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 tight sentences: the scope and condition come first, the call pattern and safety note follow. No filler, nothing repeated from the schema or annotations.

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 two-parameter tool with full schema coverage and no output schema, the description covers purpose, trigger, polling behavior, and side-effect scope. The only gap is what the progress report actually returns on subsequent calls.

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% — both chatId and connectionId are documented inline, including where to obtain them. The description adds only the 'single conversation' constraint, which is already implied by the singular required chatId, so baseline 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 and resource ('Re-read ONE of your LinkedIn conversations from its beginning') and scopes it to a single conversation, which separates it from a bulk/other resync or a plain get_chat read. The 'ONE' emphasis and 'history looks incomplete' condition make the intent unambiguous.

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?

Gives a clear triggering condition ('when its history looks incomplete') and explains the repeated-call pattern (first call starts, later calls poll progress). It does not name the obvious alternatives (get_chat, list_chat_messages, resync_attendee_chats), so the when-not-to-use side is left implicit.

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