linkfetch_list_conversations

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the Cloud-mode/authentication prerequisite, but says nothing about pagination behavior, result ordering, rate limits, or the fact that the call is read-only.

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 tight sentence with the resource front-loaded and the prerequisite in a parenthetical. No waste, though it is arguably under-specified rather than genuinely concise.

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 and no annotations, and the description does not say what a conversation record contains or how cursoring works. It is adequate for selection but thin for confident invocation of a paginated, multi-category listing tool.

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 only 33% (just next_cursor is documented), so the description must compensate and does not. It never mentions count (max 50), the category enum with its inbox/spam/inmail variants, or default paging semantics.

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 gives a specific verb and resource: 'List the user's LinkedIn inbox conversations'. It is clearly distinguishable from the sibling linkfetch_read_conversation (list vs. read a single thread), though it does not name that sibling 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?

It states a required context ('needs Cloud mode — LinkedIn connected in LinkFetch'), which tells the agent when the tool is callable. However, it gives no guidance on when to prefer this over linkfetch_read_conversation or what to do when the prerequisite is unmet.

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