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

Goes well past the annotations by disclosing a hard cost model: each successful call and each further page consumes a daily search allowance that resets at 00:00 UTC, with tier-specific quotas (50/150/300). For an agent that may page results or retry, this is exactly the kind of budget information the readOnly/idempotent hints cannot convey.

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?

Purpose and the drafting use case are front-loaded, then the author shortcut, then the quota constraint last. The quota sentence is long but each clause (per-page counting, reset time, tier numbers) carries distinct information, so nothing is padding.

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 13 optional parameters, full schema coverage, and an output schema to describe returns, the remaining gaps an agent would care about are cost and filtering semantics — both covered. No contradiction with openWorldHint=false or idempotentHint=true is implied by the cursor-based paging.

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% and the schema descriptions already explain the query, author, date, and default behaviors in more detail than the description does. The description's one parameter statement ("Set author to read the posts one creator wrote") largely repeats the schema, so it adds value only by highlighting the most decision-relevant parameter; baseline 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?

States a specific verb and resource ("Search LinkedIn posts from other creators") plus the intent ("use as inspiration"), which is far more than a restatement of the name. It doesn't explicitly contrast itself with lookalike siblings such as find_posts_to_comment or find_comments_to_reply, so an agent must infer the boundary from the word "inspiration".

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?

"Use it before drafting to ground new posts in proven formats and angles" gives a concrete usage context rather than leaving timing implicit, and the author sentence tells the agent when to use that filter versus free-text query. No competing sibling is named and no when-not-to-use condition is given, which keeps it out of 5 territory.

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