list_conversations

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

Annotations already declare readOnlyHint, idempotentHint and a closed world, so the safety profile is covered. The description adds real behavioral value in stating the result ordering (most recently active first), which is not derivable from the schema. It says nothing about pagination semantics or total counts beyond what limit/offset already imply.

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 front-loaded sentence that conveys resource, identity and ordering with no filler. It is appropriately short for a simple list tool.

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 an output schema present and full parameter documentation in the schema, plus annotations covering safety, the description covers what is needed to call the tool correctly. Minor gap: no hint about paging through results or what a default listing contains.

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 every parameter (limit, since, folder, participant, offset) is already documented in the schema and the baseline is 3. The description adds no syntax, format, or matching-behavior detail (e.g. how 'participant' text matching works) beyond what the schema already says.

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 ('List LinkedIn message conversations') plus the sort order ('most recently active first'), which an agent can use immediately. It does not explicitly distinguish itself from get_conversation or search_messages, but the plural/list framing makes the distinction inferable.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the siblings (search_messages, get_conversation) that an agent would otherwise have to disambiguate against. The only directional hint is the default recency ordering, which is implicit rather than stated as a selection criterion.

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