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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description meaningfully adds beyond that: it is LinkedIn-only, free to run, returns third-party reference posts rather than drafts, and clarifies that an empty result means no match rather than no user posts. It does not describe pagination or ordering, but the added context is substantive.

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?

Four sentences, front-loaded with purpose before usage and constraints, and each sentence carries non-redundant information (scope, triggers, platform/cost, return semantics). It is slightly dense but no sentence is filler.

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 no output schema, the description carries the burden of explaining returns and does so conceptually: third-party reference posts, not the user's drafts, and the meaning of an empty result. It does not describe result structure or fields, but for a read-only search tool with annotations covering safety and a fully-covered input schema, it is largely complete.

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%, so all four parameters (limit, query, creator, media_type) are already documented in the schema, including the semantic-matching hint and the default of 12. The description adds no parameter-level syntax or format detail beyond what the schema provides, so the baseline 3 for a fully-covered schema 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?

States a specific verb and resource (search the shared LinkedIn inspiration corpus) and pins down scope precisely: public posts from creators the community tracks, the same set as the Inspiration > Explore tab. It explicitly distinguishes what it returns from the user's own content ('reference material and never the user's own draft'), which lets an agent tell it apart from list_posts or get_post_ideas without opening a schema.

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?

Gives four concrete when-to-use triggers (what's working in a niche, examples on a subject, how others open a post, what a named creator has posted), which is strong routing guidance. It stops short of naming the alternative sibling tools (e.g., get_post_ideas, list_posts) or stating when NOT to use it, so it is clear but not fully comparative.

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