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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description still contributes real value: newest-first ordering, the fact that each message carries its conversation id, and an explicit prompt-injection warning to treat third-party content as data. Pagination mechanics are left to the schema's cursor field.

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 compact sentences plus a safety clause; scope and ordering are front-loaded and every clause carries distinct information with no repetition of the title 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?

With no output schema, the description usefully discloses the return shape (messages are conversation-tagged, sorted newest first) and the untrusted-content caveat. Only server-side paging behavior and result-size expectations are left implicit, and cursor is documented in the schema.

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 after/before/limit/cursor/senderId/connectionId are already fully documented in structured fields, and the description adds no syntax or filtering detail beyond them. The 'since yesterday' phrasing only loosely gestures at the `after` parameter.

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 ('Read your LinkedIn messages') plus scope and ordering ('across ALL conversations, newest first'), which implicitly separates it from single-thread siblings like get_conversation or list_chat_messages. It stops short of naming an alternative outright.

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?

Offers one concrete scenario ('what came in since yesterday'), which implies when to reach for it, but gives no when-not guidance and never names the per-conversation or inbox siblings an agent would need to choose between in this crowded toolset.

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