ghl_ad_li_campaign_group_publish

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

The description adds real context beyond annotations: the exact POST endpoint, version header, and required adPublishing.write scope. However, it does not say whether publishing is synchronous or async (sibling ghl_ad_fb_campaign_publishing_progress_get hints publish may be a job), what happens if the group is already published, or whether the operation can be reversed.

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 and short, but the first two lines restate the same thing ('Publish ad campaign group' / 'Publish a LinkedIn ad campaign group and push it live'), and the endpoint/spec-source metadata is verbose boilerplate.

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 two-parameter mutation with annotations covering safety hints, the description supplies the endpoint, version, and OAuth scope, which is close to what an agent needs. The main remaining gap is the async/return behavior of the publish call.

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 coverage is 100% with both adId and the nested locationId described in the schema, so the baseline applies. The description adds no meaning about the adId/body relationship or what locationId controls in a publish call.

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 ('Publish a LinkedIn ad campaign group and push it live'), and the LinkedIn qualifier plus the publish verb separate it from siblings like ghl_ad_li_campaign_group_upsert and ghl_ad_fb_campaign_publish.

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?

Usage is only implied by 'push it live' and the OAuth scope line. There is no explicit when-to-use rule versus upsert (create/update the campaign group first?) or versus the reporting/progress siblings.

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