ad_manager_li_publish_campaign_group

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

Annotations provide only generic flags (e.g., openWorldHint=true, destructiveHint=false) with no explanatory context. The description itself discloses no behavioral traits—no side effects, no permission requirements, no reversibility, no return semantics. For a mutation tool with such minimal annotation text, the description carries the full burden and fails to meet it.

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 a single short sentence, but it is essentially a title restatement. This is under-specification rather than conciseness—there is no front-loaded critical information to help the agent decide or act.

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?

Given the tool has 2 parameters, no output schema, and nontrivial domain context (ad management on LinkedIn), the description provides almost nothing. An agent cannot infer what publishing does, what state it changes, or what a successful call looks like.

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 schema covers 100% of parameters with descriptions ('Ad identifier', 'Location identifier Defaults to GHL_LOCATION_ID'), so the baseline is 3. The description adds no parameter-level insight beyond what the schema already provides, which is acceptable given full coverage.

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 'Publish ad campaign group' restates the tool name with no additional specificity. It provides a verb and resource but no detail on what publishing entails, who it's for, or what distinguishes it from sibling tools like ad_manager_li_upsert_campaign_group or ad_manager_li_update_ad_status.

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?

No guidance is given on when to use this tool versus alternatives. The description makes no mention of prerequisites, conditions, or exclusions, leaving the agent to guess when publishing a campaign group is appropriate.

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