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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is met. The description adds value beyond them: result ordering, the lightweight (preview-only) nature of each item, the enumerated preview fields, version limitation to 'posts', and the pagination contract. It doesn't discuss auth scopes or rate limits, but for a read-only listing those are minor.

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 with zero filler: capability and ordering first, return shape second, alternative and pagination last. Every sentence earns its place and the most important information is front-loaded.

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 compensates by enumerating the preview fields (activityUrn, postUrl, author, text snippet, relative time) and explaining pagination termination via nextStart. Combined with the two fully-documented parameters, an agent has everything needed to call it 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 the baseline is 3. The description's pagination note largely echoes the schema's own 'use nextStart as start' text, and the type restriction is also documented in the enum description, so it adds little beyond 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?

States a specific verb+resource ('List items the connected user has saved on LinkedIn') plus ordering semantics ('most recent first'). It scopes the current capability ('v1 supports type "posts"') so the agent knows exactly what comes back and can distinguish it from siblings like linkedin_get_person_posts or linkedin_get_my_engagement.

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?

Explicitly routes the agent to the alternative ('Use linkedin_get_person_posts to fetch full post detail for any returned activityUrn') and states the condition that selects it. It also gives the pagination procedure ('passing the nextStart from a prior response as start'), so both when-to-use and how-to-iterate are covered.

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