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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive), so the lower bar applies; the description adds real value on top by specifying sort order and the exact fields each item returns. With no output schema present, documenting the return shape and the nextStart-to-start handshake is meaningful behavioral disclosure.

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?

Three sentences, front-loaded with purpose, then return shape, then pagination. Every sentence earns its place with no redundancy or filler.

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 and only two simple parameters, the description covers purpose, sort order, return fields, and paging, and annotations cover safety. The one small gap is end-of-list behavior (what nextStart is on the final page), but otherwise an agent has what it needs to call and page correctly.

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 both parameters are already documented, giving a baseline of 3. The description restates the nextStart-to-start pagination flow but adds no format or constraint detail beyond what the schema says, so it does not exceed 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?

Names a specific verb and resource ('List the posts that the connected user saved on LinkedIn') and adds scope ('most recent first'), which no sibling tool shares. An agent can distinguish it immediately from linkedin_get_my_engagement, linkedin_get_post_comments, and the other list/get tools without opening a schema.

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 purpose implies the use case (retrieve saved posts) and the pagination sentence gives a concrete follow-up action, but there is no explicit when-to-use/when-not guidance or named alternative. This is acceptable given no sibling covers saved items, but the description leaves usage to inference.

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