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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by stating the tool returns 'recent messages' and that it should be used to understand 'prior context, commitments and tone' — behavioral context about what the agent gets. It doesn't contradict annotations. It doesn't mention rate limits or pagination, but for a read operation with strong annotations, this is solid.

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 description is two sentences with zero waste. The first sentence states the action and scope; the second gives the usage context. It is front-loaded with the core purpose and immediately useful for an agent deciding whether to call this tool.

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 read-only tool with no output schema, the description covers the core purpose and usage context. The parameter schema is extremely detailed, covering the tricky chat_id vs person name distinction and the account_id disambiguation. The only minor gap is that it doesn't describe the exact return shape or message ordering, but for a conversation read tool this is acceptable given the annotations and schema richness.

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 both parameters thoroughly. The description adds context by explaining the purpose of reading the conversation, which helps the agent understand why chat_id matters. The chat_id parameter description is exceptionally detailed, covering what to pass, what not to pass, and how to obtain it. The description itself doesn't add much beyond the schema, but the schema is so rich that the baseline 3 is exceeded slightly by the 'prior context, commitments and tone' framing.

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 states a specific verb ('Read'), a specific resource ('LinkedIn private conversation'), and the scope ('plus recent messages'). It also names the intended use case ('before replying'), which distinguishes it from sibling tools like linkedin_list_conversations and linkedin_list_inbox_chats. The title reinforces the same clear purpose.

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?

The description explicitly says 'Use before replying so the agent understands prior context, commitments and tone.' This gives a clear when-to-use directive. It also implicitly distinguishes from listing tools by focusing on reading a single conversation's content. The parameter description for chat_id further clarifies what to pass and what not to pass, which is usage guidance.

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