linkfetch_read_conversation

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

With no annotations, the description carries the full burden; it partially discharges it by disclosing the Cloud-mode requirement for the URN input form. It says nothing about read-only/rate-limit behavior, whether messages come newest-first, or how results relate to the `before` cursor's paging direction.

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?

A single sentence with zero padding; the core action is front-loaded and the two accepted identifier forms plus the mode caveat are packed into one line.

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 read tool with no output schema and no annotations, the description covers the input contract adequately but leaves the return shape (individual messages, ordering, cursor behavior) and the thread-id vs URN trade-off largely for the agent to assume.

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 baseline is 3 – the schema already documents both `thread` and `before` with formats and semantics. The description adds only the Cloud-mode caveat for URNs, which is real but marginal added meaning.

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?

Names a specific verb and resource: read messages in one LinkedIn conversation, plus the accepted identifier formats (`2-…` thread id or full URN). It is distinguishable from linkfetch_list_conversations by the word 'one', but it never names that sibling or states the relationship explicitly.

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 only implied – an agent infers this is the follow-up to listing conversations, but no when-to-use or when-not-to-use guidance is given. The one concrete constraint offered is that the URN form requires Cloud mode, which is a genuine prerequisite but not a routing rule.

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