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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds that each PDF is fetched from its URL and stored as a DOCUMENT asset, which reinforces the open-world/network behavior. It says nothing about failures mid-batch (partial uploads), duplicate handling, size/page limits, or whether re-uploads create new assets.

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 sentences, with the core action and target front-loaded and the mechanism (download-then-upload) following. No filler, though the second sentence largely restates the first's 'upload' action with added mechanics.

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 no output schema, the description should say what the agent gets back (e.g., asset IDs/handles usable in create_update_document_ad). It also omits batch failure semantics for the required array of URLs, leaving a meaningful gap for a mutation tool that an agent must chain into ad creation.

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% and both parameters are documented inline, including the URL format, PDF content-type requirement, and the order-alignment rule for names. The description adds no parameter detail beyond that, 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?

States a specific verb and resource ('Upload PDF documents to the Metadata platform library') and the downstream purpose (promotion as LinkedIn Document Ads). It distinguishes itself implicitly via 'PDF' from upload_image_creative and upload_video_creative, but never names or contrasts those siblings directly.

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 intended use case — building a library asset for Document Ads — is implied clearly enough to act on. However, there is no explicit when-to-use/when-not guidance, no mention of how it differs from upload_image_creative/upload_video_creative, and no note that the returned asset still needs create_update_document_ad.

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