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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the description's 'Read-only' merely restates structured data. It discloses nothing new: not whether results are account-scoped, whether the set is paginated, or how these IDs relate to a subsequent search.

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?

Two short sentences with no wasted words, but the brevity comes from under-specification rather than discipline. The first sentence is a dependent fragment ('Ids LinkedIn expects...') that lacks a subject or verb, harming front-loading of the actual action.

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, an undocumented nested parameter, and zero schema descriptions, the description carries the full explanatory burden and delivers almost none of it. An agent knows it is a safe read but not what it returns, how to scope it, or where the resulting IDs are consumed.

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 0% for two parameters, including a required account_id UUID and a nested free-form 'extra' object. The description mentions neither, so it fails to compensate for the coverage gap, and the purpose of the open-ended 'extra' bag remains entirely unexplained.

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 description adds a fragment of meaning beyond the title: the tool yields LinkedIn IDs to be used in place of raw search text. But it never states the action or the object (list? resolve? lookup?), so an agent cannot confidently distinguish it from search_linkedin or other list_* tools without opening the 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?

No when-to-use guidance, no prerequisites, and no mention of which sibling consumes the returned IDs. The phrase 'instead of raw search text' hints at a relationship with search, but the agent must infer that this tool should be called first and its output fed into a search call.

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