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

With no annotations, the description carries the full load and delivers real behavioral context: exact default asset counts, the fact that tier changes credit cost and UGC quality but not asset counts, and that regenerateAsset consumes credits only. It omits auth/permission requirements, async/status behavior, and what deleteFromLibrary does to already-downloaded 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?

Front-loaded with purpose, then defaults, then tier semantics, then the action list — a sensible ordering. The restatement of the action enum that the schema already supplies is mild redundancy, but the surrounding text is dense and information-bearing.

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 seven-action tool with no output schema and no annotations, this covers the essentials: what gets generated, how tiers affect cost/quality, and where to find action parameters. It does not cover response shape, polling/status flow, or credit magnitudes, but the pointer to adgpt_capabilities fills a large part of the gap.

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 description adds meaning to several enum values ('Re-render one image', 'remove a campaign from your library', 'download'), which the bare enum does not convey. But the entire 'params' object is delegated to adgpt_capabilities, so at 50% schema coverage the description resolves only the action parameter and leaves the substantive inputs opaque.

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?

Uses a specific verb+resource ('Generate and manage Full Campaigns (FC)') and enumerates the three input modes (product URL, manual product, text-only) plus the default asset bundle. It implicitly differentiates from siblings like adgpt_single_asset and adgpt_ugc by describing the full-bundle scope, but it never names or contrasts them explicitly.

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 action enum is surfaced as a usage menu and the description points to adgpt_capabilities for per-action parameters, which is useful routing. However, there is no explicit when-to-use guidance relative to siblings (e.g. single asset vs full campaign vs social), and no prerequisites or exclusions are stated.

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