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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so safety is covered. Beyond that the description adds almost nothing: it does not say results are capped to the top N by engagement (limit is per-the-schema), does not mention sorting when engagement_trigger is supplied, and offers no rate-limit, pagination, or empty-result context.

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?

A single front-loaded sentence with zero filler, and the scope qualifier is placed up front. It is efficient, but at one short sentence it leans toward under-specification rather than model conciseness for a five-parameter tool in a multi-step workflow.

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 100% schema coverage and no output schema, the structured fields do most of the work, so the bar is moderate. However, this tool sits inside a three-step LinkedIn retargeting flow (list source types -> search sources -> create audience) and the description never states that ordering, leaving the agent to reconstruct it from parameter text.

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%, so the baseline of 3 applies; each parameter's meaning, enum, defaults and the engagement_trigger/lookback_window_days pairing are fully documented in the schema itself. The description only echoes the required engagement_source_type constraint ('for a chosen engagement source type') and adds no syntax or format detail beyond the schema.

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?

Specific verb ('Find') plus a specific resource ('LinkedIn campaigns or pages' as retargeting sources) scoped by a 'chosen engagement source type'. An agent can tell this is a candidate-discovery call rather than a create/list-types call, though it never names the closest siblings (get_linkedin_engagement_source_types, create_linkedin_engagement_retargeting_audience) to sharpen the boundary.

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 phrase 'to retarget, for a chosen engagement source type' implies this is a pre-step before building a retargeting audience, but that workflow is only inferred. There is no explicit when-to-use / when-not-to-use statement and no mention of the required prerequisite call to get_linkedin_engagement_source_types, which lives only in the schema text.

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