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

Without annotations, the description carries the full burden for disclosing behavior. It does mention that it returns engagement metrics, author info, images, videos, and articles, which gives insight into the output. However, it does not disclose any limitations, side effects, or contextual details such as rate limits, authentication requirements, or the fact that it returns only a limited window of recent posts. This is moderate transparency for a read-only tool.

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 a single sentence that covers the core action and the main return payload. It is front-loaded with the most important information and contains no redundant or extraneous phrases, earning a top score for efficiency.

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 that there is no output schema, the description does a decent job of outlining what results are included (engagement metrics, images, videos, articles). It also aligns with the schema for pagination via the 'page' parameter, which is described. It could be more complete by mentioning the sentiment analysis option or any limitations, but overall it provides sufficient context for a simple read tool.

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 the parameter descriptions in the input schema fully document each parameter. The tool description adds minimal semantic value beyond the schema—it rephrases the 'url' parameter as 'profile URL or public slug', which is already stated in the schema. Since the schema already does the heavy lifting, the baseline of 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 clearly states the tool's function with a specific verb ('Get') and resource ('recent posts authored by a LinkedIn person'), and distinguishes it from sibling tools like linkedin_company_posts by specifying 'person' rather than 'company'. It also lists the types of content returned (engagement metrics, author info, images, etc.), making the purpose unambiguous.

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 description gives clear context: this is for retrieving posts by a LinkedIn person using a URL or slug. It does not explicitly mention when not to use it or name alternatives, but the sibling context (e.g., linkedin_company_posts, linkedin_post_details) and the phrase 'authored by a LinkedIn person' imply the appropriate use case. This falls between 'clear context, no exclusions' and 'implied usage,' warranting a 4.

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