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

Adds substantial context beyond the readOnly/idempotent/openWorld annotations: the 10-credit cost per call, the warning that each paginated page is charged again, and the cursor-based pagination model. Cost and re-charge behavior are exactly the operational facts an agent cannot infer from annotations or schema.

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 short sentences, front-loaded with the core operation, then cost warning, then efficiency advice, then pagination mechanics. No filler; every sentence conveys a distinct, actionable fact.

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 3-parameter read tool with an output schema already defining return values, the description covers what matters: scope, cost model, narrowing via `type`, and pagination. Only `url` format remains slightly underspecified, which is a minor gap.

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 0%, so the description must carry parameter meaning. It explains `type` well (the four activity kinds) and fully explains `cursor` (pass the previous response's cursor), but the required `url` parameter is never clarified — it is only implied by 'a LinkedIn person', leaving format/expectations unstated.

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 (fetch) and resource (a LinkedIn person's recent posts, comments, reactions, articles), enumerating the activity kinds. This cleanly separates it from siblings like get_company_posts, get_person_profile, or get_post, which operate on different entities.

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?

Gives concrete usage guidance: prefer a single call, use `type` to narrow instead of fetching everything and filtering, and pass the cursor to paginate. It does not explicitly contrast with the closest alternatives (e.g., when to use get_person_profile instead), so it stops short of full routing guidance.

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