ghl_ad_fb_campaign_publish

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which the description supports by stating 'push it live'. The description adds the endpoint and OAuth scopes, but does not explain side effects (e.g., whether the operation is irreversible) or rate limits. It adds some context beyond annotations but not extensively.

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 relatively concise (5 lines) and includes key operational details (endpoint, OAuth scopes). However, the first line 'Publish campaign' is redundant with the title, slight optimization possible.

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 simple tool with 2 parameters and no output schema, the description provides the endpoint and OAuth scopes, which are essential for invocation. It also states the effect ('push it live'). Missing details like response format or error handling, but adequate for basic use.

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 descriptions and examples for both parameters. The description does not add any additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 explicitly states 'Publish a Facebook campaign and push it live to Facebook', which clearly identifies the action (publish) and the resource (Facebook campaign). This distinguishes it from sibling tools like pause, resume, or delete.

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 does not provide any guidance on when to use this tool versus alternatives. It lacks conditions, prerequisites, or comparisons to sibling tools such as ghl_ad_fb_campaign_pause or ghl_ad_fb_campaign_upsert.

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