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 safety profile is covered. The description adds non-obvious behavioral context beyond that: the closed-set nature of some facets, that query filters locally rather than remotely, and how results feed downstream campaign tools. It stops short of describing pagination or result-list size.

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 purpose is front-loaded and the two facet categories are clearly labeled, so it scans well. It is on the long side and uses arrows and parentheticals ('urn:li:geo:…', '(10: Unpaid…Owner)'), but nearly every sentence carries actionable semantics rather than 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?

For a two-parameter read-only lookup tool with an output schema present, the description covers everything needed to call it correctly: valid facet values, query semantics per facet class, and downstream usage. Return-value formatting is legitimately delegated to the output schema.

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% and the schema lists only bare 'facet' and 'query' with defaults, so the description carries the full burden. It compensates thoroughly: it enumerates all valid facet values, explains the default, clarifies that query is optional for fixed-list facets and filters locally, and gives a concrete example (facet=locations query='İstanbul').

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 states a specific verb and resource ('Searches LinkedIn targeting entities by name') and immediately explains the role of the output ('returns the URNs you pass to create_linkedin_campaign / update_linkedin_campaign_targeting'). This clearly distinguishes it from sibling search tools like tiktok_targeting_search, microsoft_location_search, and geo_target_search.

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?

Explicitly splits facets into SEARCHABLE (must give a query) and FIXED-LIST (query optional, leave empty for full set) and shows the exact call pattern with a worked example ('call facet=seniorities with no query, read the URNs off the returned list'). It tells the agent when to supply a query and when not to, which is precisely the decision an agent must make.

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