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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavior: results are URNs (identifiers, not display strings) and empty-query behavior differs by facet type. That enumeration semantics is a real behavioral trait beyond structured fields, though there is no mention of result volume, pagination, or limits against LinkedIn's lookup service.

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?

The critical statement is front-loaded, but the facet list duplicates the 26-value enum verbatim and pads the opening sentence. The mandatory disclaimer with full Arabic translation is required content, yet it is long and placed after the technical text, making the whole description heavier than it needs to be.

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?

For a read-only lookup tool with no output schema, the description does the essential work: it explains that results are URNs, which facets are enumerable, and how empty queries behave. Only the behavior of `limit` and any result-volume expectations are missing, which are minor gaps for this kind of resolver.

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 only 50%, so the description needs to compensate and it partly does — it clarifies facet semantics and the empty-query behavior of `query`, and its 'in their language' phrasing hints at the `language` parameter. However, `limit` is undocumented in both schema and description, and the long facet roll-call merely restates the enum values already in the schema, so the net semantic gain is moderate.

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 ('Find LinkedIn targeting values (URNs) by name') and enumerates the facet families it resolves. An agent can distinguish it immediately from siblings such as linkedin_reach_estimate or linkedin_campaigns, since this is the resolver, not the estimator or the campaign reader.

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?

The description gives a concrete usage rule for the key case: enumerated facets (seniorities, job_functions, company_sizes, ages, genders, languages, years_of_experience) list every value when query is empty, which tells the agent when to pass a query vs. when to browse. It does not explicitly say when NOT to use it or name an alternative flow (e.g., reuse cached URNs), so it stops short of full alternatives guidance.

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