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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses async execution, deduplication behavior, automatic daily sync, storage semantics (metadata + thumbnail, not full assets), and that assets remain on Meta. This gives an agent a clear picture of side effects and non-destructive behavior.

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 description is four dense sentences with no filler. It front-loads the core action and scope, then efficiently covers execution mode, progress tracking, deduplication, sync behavior, storage implications, and reusability. Every clause adds useful information.

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 single-parameter async import tool, the description covers trigger, background execution, progress checking, deduplication, post-import sync, storage behavior, and downstream use. The only minor gap is that it never explicitly states what the initial call returns (e.g., an import job ID), though pointing to adsap_get_import_status is a useful substitute.

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?

The only parameter, ad_account_id, is already fully documented in the schema with a pattern and description. The tool description does not add parameter-level detail, but with 100% schema coverage the baseline of 3 applies; no additional compensation is needed.

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 specific verb and resource: 'Import ALL historical creative assets (images + videos) that already exist in a Meta ad account into the ADSAP Creative Library.' It clearly identifies source, destination, asset scope, and differentiates this bulk import from sibling tools like adsap_upload_creative or adsap_list_creative_assets.

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 gives clear usage context: it runs in the background, users should check progress via adsap_get_import_status, and after the first full import a daily sync handles new assets. It does not explicitly contrast with manual upload tools or state when not to use it, but the guidance is strong enough for an agent to know when this bulk import is appropriate.

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