Get recent posts by a person or company

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds valuable behavioral context: credits cost (4 per page), realtime option with surcharge, domain resolution credit refund, pagination via cursor, and return fields. No contradiction with annotations.

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 somewhat lengthy but well-structured with clear sections. Each sentence adds value. Could be slightly more concise but still effective.

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?

Given output schema exists, description thoroughly covers pagination, credits, entity resolution, and usage scenarios. It provides complete context for an agent to select and invoke correctly, including limitations and alternatives.

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 coverage is 100%, so baseline is 3. Description adds meaning beyond schema: explains identifier types (URL, slug, URN, domain) and company resolution behavior; clarifies freshness enum behavior and trial restrictions; explains max_credits as a ceiling. Notably enhances clarity.

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 description clearly states it fetches recent LinkedIn posts of a person or company. It distinguishes from sibling tools like linkedin_get_company by referencing domain resolution behavior and explicitly stating what it is not for (reading single post, keyword search).

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 states when to use: 'Use this for what has X been posting, voice-of-company research, or activity checks before outreach.' Also states when not to use: 'Not for reading one specific post you already have a URL for, and not for keyword search across LinkedIn.'

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