ghl_ad_fb_adset_upsert

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds the endpoint and OAuth scopes, which are useful but do not significantly expand on the behavioral traits beyond the annotations. The 'upsert' behavior is implied but not elaborated (e.g., what fields are overwritten).

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 extremely concise with three lines: a summary, a one-line explanation, and endpoint/scopes. No superfluous text. It is well-structured and front-loaded.

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?

Despite the detailed schema, the description lacks information about return values (e.g., the created/updated adset ID or status). Since there is no output schema, the description should at least hint at the response. Additionally, it does not mention required integrations or permission checks.

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 input schema is fully described (100% coverage) with detailed properties and examples. The description does not add any additional meaning beyond what the schema already provides. According to the scoring guidelines, with high schema coverage, baseline is 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 the resource ('adset') and the action ('upsert' meaning create or update). This distinguishes it from sibling tools like ghl_ad_fb_adset_delete, ghl_ad_fb_adset_duplicate, etc.

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 alternatives. There is no mention of prerequisites, such as the need for an existing Facebook integration or campaign. The description merely states what the tool does without context.

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