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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely valuable context beyond that: it warns that names, headlines, messages and post text are third-party content to treat as data rather than instructions — a prompt-injection guard specific to this tool's payload.

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 capability and its return fields are front-loaded, and the second sentence is a security notice rather than filler. Nothing is repeated from the title or schema, and there is no 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?

There is no output schema, but the description compensates by naming the fields returned, and the read-only safety profile is covered by annotations. The remaining gap is that it does not clarify its relationship to get_conversation, which given 200+ siblings is the one thing an agent could still get wrong.

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% and both parameters are documented in-schema, including where chatId comes from and how connectionId resolves. The description adds no parameter detail beyond the schema, so the 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?

Specific verb and resource: 'Read ONE of your LinkedIn conversations by id', plus it enumerates the returned fields (who it is with, subject, unread count, last activity). The 'ONE' contrasts implicitly with list_chats, but the description never distinguishes it from the closely related get_conversation sibling, so the agent must guess between them.

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?

Usage is implied through 'by id' and the schema note that chatId comes from list_chats, so the prerequisite listing step is discoverable. But there is no explicit when-to-use guidance versus get_conversation or get_message/list_chat_messages, which is a real ambiguity in this large sibling set.

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