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

With no annotations, the description carries the full burden and does so well: it declares reads-only, no drafts, no profile opens, an explicit cost model ('the cost is the same whether it returns 1 post or 50'), ordering (newest first), and that reposts are dropped. It omits any statement about auth/permission prerequisites or rate limits, which keeps it off a 5.

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?

Well front-loaded and sectioned (scope → USE → DO NOT USE → Args → Returns), so an agent can scan it quickly. Minor waste: the title is restated verbatim at the top, and the '#hiring post vs profile badge' distinction is made twice, though the repetition is defensible given the stakes.

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 six-parameter tool with no annotations and no output schema, the description supplies everything needed: full parameter semantics, the return shape ({posts, count, has_more} with per-post fields), and a hand-off hint that prof_ handles feed get_linkedin_profile or schedule_dm_to_person. Nothing an agent needs to call or chain this tool is missing.

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?

Despite 0% schema description coverage, every one of the six parameters is explained with meaning beyond the schema: keywords is post-body text (and hashtag-in-post ≠ profile badge), author_company and author_keywords are author-side filters, date_posted enumerates values with default and sort order, posted_by defines the network scope, and limit gives range, default, and the repost-dropping behavior.

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?

States a specific verb and resource ('Search LinkedIn posts by topic') plus the exact output contract: each post returned with its author as a candidate. The second paragraph makes the distinction from people-search siblings (search_prospects, find_prospects) unmistakable.

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?

Explicit 'USE THIS when' with three concrete query examples, plus a 'DO NOT USE' clause naming the alternatives (search_prospects / find_prospects for topic-less people search, discover_prospects for message writing). It even resolves the subtle case of posted-about-hiring vs profile #hiring badge, which is exactly where an agent would otherwise pick the wrong tool.

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