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

With readOnlyHint=true and openWorldHint=true already present, the description adds substantial behavioral context: the sign-in gate, the no-authenticated-session policy, and the choice to report the gate instead of a 404. It also mentions cost, though 'unbilled answer' and 'Costs 1 credit' sit in slight tension.

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 key constraint is front-loaded in the second sentence, and the rationale is compact enough for a tool with an unusual failure mode. Some phrasing, especially the unbilled/cost wording, could be tighter.

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 tool with no output schema and partial parameter documentation, the description covers the critical behavior: it will not return real posts and instead reports the gate. It could be more complete by clarifying whether any search results are ever possible or exactly what the gate response looks like.

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 75%, with query, cursor, and date_posted documented and cache_max_age undocumented. The description does not add any parameter-level meaning, so it neither compensates for the gap nor detracts from the mostly self-documenting schema.

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 names a specific verb and resource (keyword search over LinkedIn posts) and explicitly states the unusual realization: the endpoint reports LinkedIn's sign-in gate rather than returning posts. This distinguishes it from sibling tools like linkedin_post and linkedin_companyPosts, though it does not explicitly compare itself to them.

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?

It explains the operational context (LinkedIn gates content search, no authenticated scraping) and why the tool exists, but gives no explicit when-to-use guidance against alternatives or a clear recommendation to avoid calling it. The intended usage is implied rather than stated.

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