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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the mutation profile is known. The description adds nothing beyond that — it restates the name/title and does not explain that updating overwrites the ad, that all four required fields must be resupplied on update, or what happens to unspecified fields. For a destructive, open-world write, that is a meaningful gap.

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 no redundancy or filler. It is efficiently structured, but the brevity borders on under-specification rather than true economy.

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?

This is an 8-parameter destructive mutation tool with no output schema. Given that the description is one sentence and leaves create-vs-update mechanics, required-field implications on update, and the return shape entirely to the schema, it is not complete enough for the complexity.

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%, including the enum meanings, maxLengths, defaults, and even the note that libraryId is not an image/video id. The description contributes no additional parameter meaning, so the 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?

The description uses a clear verb pair (create/update) and names a specific resource (LinkedIn Document Ad on the Metadata platform), which inherently separates it from create_update_image_ad, create_update_video_ad and create_update_carousel_ad. It stops short of explicitly routing the agent away from those siblings, so it is clear but not fully differentiated.

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 offers no when-to-use guidance: nothing about how to choose create vs. update (the id parameter in the schema carries that logic, not the description), no prerequisite that a DOCUMENT creative must already exist in the library, and no mention of alternatives. The agent must open the schema to learn the mode switch.

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