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

Beyond the annotations, the description discloses important behavior: the provider publish is PAUSED, spend requires activation, and a failed publish preserves the draft for retry. It does not cover auth or rate limits, but adds substantial operational context for a write/destructive tool.

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 dense but front-loads the core action and paused-publish behavior before platform details. The platform and creative lists are lengthy, but they carry necessary invocation guidance for a multi-provider campaign tool.

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 complex 12-parameter write tool with no output schema, the description covers the main behavioral and parameter requirements across providers. Remaining gaps around a few simple parameters and auth context are minor given the rich annotations.

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?

With 0% schema description coverage, the description compensates well for the complex parameters by explaining account/website identifiers, goal enums, daily budget currency, platform-specific creative requirements, and META creative variants. It leaves title, start/end date, and custom URL implicit, but the major ambiguities are addressed.

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 states a specific verb and resource: create an ad campaign draft and publish it paused. It distinguishes this tool from activate_ads_campaign and publish_ads_campaign by explaining the paused state and retry flow.

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?

It clearly explains that the campaign is created paused and cannot spend until activate_ads_campaign, and that a failed publish should be retried with publish_ads_campaign. Platform-specific goal and creative requirements further guide use, though explicit exclusions are not stated.

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