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

Annotations already declare openWorldHint=true, readOnlyHint=false and destructiveHint=false, so the write/external-call profile is covered. The description adds the constraint that criteria must be LinkedIn-supported, but says nothing about persistence, what is returned on success (audience ID vs. estimate count), or failure modes when criteria are unsupported.

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, front-loaded with the action and resource. The second sentence is partly redundant with the first ('LinkedIn-supported targeting criteria' then a list of those criteria), which keeps it just short of a 5.

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 an 8-parameter mutation tool with no output schema, the description omits what the agent gets back (new audience identity, estimated size) and whether the created audience is immediately usable for targeting. The rich schema compensates for parameters, but return-value behavior is left unexplained.

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%, with each parameter carrying enums, examples and formats. The description's list of criteria categories mirrors the schema fields and adds no syntax, format or validation detail beyond it, so baseline 3 applies.

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?

Clear verb+resource: 'Create a LinkedIn native criteria audience using LinkedIn-supported targeting criteria.' The word 'criteria' implicitly distinguishes it from create_csv_upload_linkedin_native_audience and create_g2_intent_linkedin_native_dynamic_audience, but that contrast is never made explicit.

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 says what an audience can be built from but never states when to choose this tool over the many sibling audience-creation tools (CSV upload, Facebook native criteria, LinkedIn engagement retargeting, G2 intent). The important estimate_only preview workflow is documented only in the schema, not surfaced as usage guidance.

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