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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the read-only sentence is largely confirmation. The genuinely additive disclosure is the pricing model — 1 credit per result with a 1-credit minimum per request — which is cost information an agent cannot get from any structured field and which affects how it should size the `count` parameter.

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 short sentences, front-loaded with purpose, then safety, then cost — nothing is buried. The middle sentence restates the readOnlyHint annotation almost verbatim, which is minor redundancy but not wasteful enough to undercut the structure.

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 five fully documented parameters, no output schema, and annotations covering the safety profile, the description supplies the one missing operational fact: cost per request. It does not describe what a returned post contains or how pagination via `start` behaves, but there is no output schema to lean on, leaving a small 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 100%, with every parameter including `count`, `start`, `sortOrder`, `datePosted`, and `keyword` documented inline, including enums and ranges. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 gives a specific verb and resource ("Search LinkedIn posts"), so an agent immediately knows the operation. It does not, however, distinguish this tool from close siblings such as linkedin_search_all, linkedin_get_posts_from_company, or linkedin_get_posts_from_profile, which could also surface posts.

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?

Usage is only implied by the verb "Search" — there is no explicit statement of when this keyword-based post search is preferred over linkedin_search_all or the profile/company post-listing tools. No exclusions, prerequisites, or alternative names are provided.

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