ghl_ad_li_campaign_group_upsert

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds that the tool includes campaigns and ads, and mentions OAuth scopes, but does not disclose additional behavioral traits like error handling, limits, or the effect of create vs update. No contradiction with 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 extremely concise: two clear sentences plus endpoint and OAuth scopes. Every piece of information serves a purpose, and the primary action is 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?

Given the complexity nested objects, many parameters, and no output schema, the description is insufficient. It does not mention what the response contains (e.g., the upserted campaign group ID), nor does it clarify that locationId is required. More detail on return values and error handling is needed.

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 each parameter having a description. The tool description adds high-level context ('Create or update a LinkedIn ad campaign group with campaigns and ads') but does not add significant meaning beyond the schema descriptions. Baseline 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 clearly states the action ('Upsert') and resource ('ad campaign group'), and specifies that it creates or updates a LinkedIn ad campaign group including campaigns and ads. This distinguishes it from sibling tools like get, publish, and reporting.

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 use for upserting LinkedIn ad campaign groups, but provides no explicit guidance on when to use this tool versus alternatives (e.g., separate create/update tools, or Facebook/Google equivalents). No when-not-to-use or prerequisite information is given.

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