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

With no annotations provided, the description has to carry the behavioral burden. It does state 'Read-only', which is the single most important trait here, but it says nothing about pagination, message volume limits, ordering, or what fields each message contains. That is a meaningful gap for a list-style retrieval tool.

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 short clauses, no filler, and the key orientation (which chat, where the id comes from) is front-loaded. Nothing in it is redundant with the name alone.

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 one-parameter read tool this covers purpose, id provenance, and non-mutation, but there is no output schema, so the description leaves the return shape (message fields, ordering, whether all history is returned) entirely unspecified. Adequate but with clear gaps.

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 0% and the single parameter is a bare string, so the description must supply its meaning. It does so by explaining that chat_id identifies one chat and should come from list_linkedin_conversations, which is more than the schema offers. It still lacks format or example detail.

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 resource and scope: all messages of a single LinkedIn chat, identified by chat_id. It also names the sibling that produces the id (list_linkedin_conversations), which separates it from list-level tools. It is not a clean verb phrase, and the title ('Open a LinkedIn conversation') is slightly off from what is described, but an agent can tell what it retrieves.

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 parenthetical 'chat_id from list_linkedin_conversations' is a useful routing hint for how to invoke the tool. However, the description gives no explicit when-to-use or when-not-to-use guidance and names no alternative for reading a chat's contents, so usage is only implied.

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