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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new operational context: public-data-only results and a credit cost of 1 per result with a 1-credit minimum per request. It stops short of describing pagination behavior or result shape, but this is solid supplemental disclosure.

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 the purpose and then the behavioral facts. "Returns public data and changes nothing" mildly duplicates readOnlyHint, but nothing is bloated and no sentence is wasted on 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?

The credit-cost disclosure is important for a metered search tool, and annotations cover the safety profile. However, with no output schema the description says nothing about what a result contains, and it omits any differentiation from the many sibling LinkedIn search endpoints. Adequate but with clear gaps for a tool in a crowded family.

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%; keyword, count (1-10, default 10) and start (offset) are fully documented in the schema. The description's "1 credit per result returned" implicitly ties cost to the count parameter, which is a small value add, but it is never explicitly connected to count or to how repeated `start` pages are billed.

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 first sentence, "Search LinkedIn services," essentially restates the tool name and title without defining what a LinkedIn "service" is. With siblings like linkedin_search_companies, linkedin_search_products, and linkedin_search_jobs, the agent gets no basis for distinguishing this resource from those. The verb and surface are clear, but the object is vague.

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?

There is no when-to-use or when-not-to-use guidance and no alternative named, despite nine sibling linkedin_search_* tools that plausibly overlap. The agent must infer selection from the tool name alone. Nothing is misleading, but no routing help is given.

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