ad_manager_fb_publish_campaign

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

The description adds no behavioral information beyond the annotations. Annotations indicate a non-read-only, non-destructive, open-world operation, but the description does not elaborate on side effects, what 'publishing' means operationally, or potential failures.

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?

While extremely short, the brevity is not effective; the single sentence adds no value over the tool name and fails to convey essential details. It is under-specified rather than concise.

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 mutating operation like publishing a campaign, the description is completely inadequate. It doesn't explain the effect of publishing, whether it requires an existing integration, or what happens on success. The output is unknown, and no context is given.

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 fully documents both parameters (campaignId and locationId) with clear descriptions, so the baseline applies. The tool description does not add any parameter-specific information.

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 campaign' simply restates the tool name's last two words, providing no additional clarity about what publishing entails or how it differs from other campaign operations (e.g., upsert, duplicate). It is essentially a tautology.

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 provided on when to use this tool versus any of its many siblings (e.g., ad_manager_fb_upsert_campaign, ad_manager_fb_pause_campaign). There is no mention of prerequisites, context, or alternatives.

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