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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior the annotations do not: page-based result delivery, the has_more/next_cursor contract, and the fact that participant search scans up to 1250 recent conversations rather than searching exhaustively.

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?

Four compact sentences ordered purpose-first, then return payload, then the participant option, then pagination mechanics. Every sentence carries information, though the return-field enumeration is the kind of detail that could be trimmed if a further sentence were needed elsewhere.

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 no output schema, the description correctly takes on the burden of naming the returned fields, and it fully explains the pagination loop an agent must implement to retrieve all results. For a read-only listing tool with six optional parameters, nothing essential to correct invocation is missing.

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 all six parameters are already documented in the schema, and the description's parameter content (participant lookup, cursor continuation) largely restates it. The one addition, the 1250-conversation scan ceiling for participant lookup, also appears in the schema, so no real value is added beyond the structured fields.

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 opening sentence states a specific verb and resource ("List your LinkedIn DM conversations (inbox)") and enumerates the returned fields, which is far more than a restatement of the title. It does not explicitly name or route away from the neighboring linkedin_get_conversation_messages tool, so the sibling distinction is left to inference.

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 implied rather than stated: the participant parameter is framed as an optional lookup path and pagination continuation is spelled out ("call again with the same arguments and cursor set to next_cursor"). There is no explicit when-to-use-this vs. when-to-use-an-alternative guidance, and no mention of when to prefer this over linkedin_get_conversation_messages.

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