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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable return context (up to ~50 posts, including text, engagement counts, and post URL), which is meaningful since no output schema exists. It does not cover pagination behavior or data freshness.

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?

Two tight sentences with zero waste: the core action and identifier options are front-loaded, followed by return details. Every clause earns its place.

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 simple read tool with 100% schema coverage, rich annotations, and no output schema, the description is largely complete: it names the resource, accepted identifier forms, and return contents. It could add a note about cursor-based pagination, but the schema already covers that parameter.

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 `identifier` and `cursor` are already fully documented in the schema. The description restates the accepted identifier formats (URL, public ID, URN), which duplicates schema content without adding new semantics. Baseline 3 is appropriate.

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 states a specific verb (Get) and resource (a person's recent LinkedIn posts), and uses "person's" to implicitly distinguish from the company-posts sibling. However, it does not explicitly differentiate from other person-focused tools like linkedin_get_profile or linkedin_get_connections.

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?

No when-to-use guidance is provided. The description never states conditions for choosing this tool over alternatives like linkedin_get_company_posts, linkedin_get_profile, or linkedin_search_people, nor does it mention any exclusions or prerequisites.

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