ghl_ad_fb_ad_upsert

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

Annotations already declare idempotentHint=true and destructiveHint=false, which the description supports by stating 'upsert' (idempotent) and 'Create or update' (not destructive). The description adds endpoint and OAuth scopes, which provide some additional context, but does not elaborate on behavior beyond the annotations.

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 concise (two sentences plus endpoint/scopes) and front-loaded with the core purpose. The endpoint and scopes are arguably extraneous for an AI agent but do not significantly harm conciseness.

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 complex nested input schema and no output schema, the description is minimal. It does not explain return values, prerequisites (e.g., existence of campaign/adset), or validation. Annotations and schema coverage compensate partially, but for a complex upsert operation, more contextual guidance would be beneficial.

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 description coverage is 100%, so the schema itself documents parameters thoroughly. The description does not add any parameter-specific meaning beyond what the schema provides, resulting in a baseline score of 3.

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 clearly states 'Upsert ad' and 'Create or update a Facebook ad', providing a specific verb and resource. It distinguishes from sibling tools like ghl_ad_fb_ad_delete, ghl_ad_fb_ad_duplicate, etc., by focusing on upsert functionality.

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 implies usage for creating or updating ads via 'Create or update a Facebook ad'. However, it does not provide explicit exclusions or compare with alternatives like ghl_ad_fb_ad_duplicate for duplication scenarios. Still, the context is clear enough given the sibling set.

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