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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the core safety profile is covered. The description adds useful behavioral context beyond the annotations by naming the exact underlying endpoints and explaining that created_before controls legacy/unused paging; this is meaningful, even though it does not discuss authorization, rate limits, or response structure.

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?

The description is a single, front-loaded sentence: it states the core action first, then compacts relevant implementation details into a short clause. There is no filler, and every segment—action, endpoint, paging hint, exact equivalent route—adds useful information without making the text bulky.

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 read-only tool with a clear schema, a complete output_schema, and no nested objects, the description provides enough context to guide correct invocation: it identifies the use case, the relevant conversation ID source, and the optional paging direction. It does not discuss ordering, default page size, or 'latest message first' behavior, but the output schema and annotations compensate for most of that.

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?

The input schema already provides 100% descriptive coverage of all three parameters, including origin and type for account_id, conversation_linkedin_id, and created_before. The description adds little beyond restating created_before as 'paging' and echoing the endpoint pattern, so it stays at the schema-covered baseline.

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 first phrase is a specific verb+resource statement: 'List messages in a LinkedIn conversation,' making the function's purpose unmistakable. It also references the exact Voyager/Kanbox/GET endpoints and the optional 'created_before' paging, which differentiates it from sibling listing tools like list_conversations.

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 description implies when to use it—when you need the messages of a specific LinkedIn conversation—and even mentions optional paging behavior. However, it does not explicitly distinguish when to prefer this tool over related sibling tools such as salesnav_list_thread_messages or react_message, nor does it document prerequisites or excluded cases.

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