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

No annotations are provided, so the description carries the full burden, and it delivers the two facts that matter most: the retrieval mechanism ('Uses Google's index') and the auth posture ('no LinkedIn login is needed'), plus the shape of the response. It stops short of noting index-coverage/freshness limitations or pagination behavior, which would be the remaining behavioral risks.

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 return contents, then the mechanism/auth caveat. Every sentence carries information the agent needs, including the return fields that no output schema supplies.

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 compensates by enumerating returned fields (snippet, author, headline, profile URL), and with full schema coverage the inputs need no further prose. It is only slightly short of complete because it does not warn about the coverage/freshness limits inherent in scraping Google's index.

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% for both parameters (query and maxResults with its default), so the schema already documents the inputs fully; the description adds no syntax, quoting, or matching-behavior detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 keyword') and immediately names the returned fields, so an agent can distinguish it from nearby siblings like search_linkedin_employees, search_linkedin_jobs, and get_linkedin_profiles without opening any 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?

Usage is implied by the resource ('posts') and the note that no LinkedIn login is required, which tells the agent this works without credentials. However, there is no explicit when-to-use/when-not-to-use guidance and no routing to alternatives such as find_linkedin_candidates or get_linkedin_profiles when a person or company lookup is actually wanted.

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