ghl_ad_li_ad_status_update

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

Annotations already indicate it's a mutation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds OAuth scopes and endpoint details, which provide additional context but no further behavioral traits like rate limits or reversibility.

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 short and front-loaded with the core purpose ('Update ad status' and 'Pause or resume...'). It includes relevant technical details (endpoint, OAuth scopes) without unnecessary filler.

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 4 parameters, nested body, and no output schema, the description provides adequate context about the tool's role in LinkedIn ad management but lacks details like the effect of ARCHIVED vs PAUSED or how isDraft modifies behavior.

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?

Input schema coverage is 100% with basic descriptions (e.g., 'Ad identifier', 'Location identifier'). The description does not add extra meaning beyond the schema, which already documents required and optional fields and their enums.

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 tool updates ad status for LinkedIn ads, campaigns, or ad groups, and specifies the actions (pause/resume/archive). This distinguishes it from sibling tools like ghl_ad_li_campaign_group_upsert or ghl_ad_li_account_delete, which have different purposes.

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 pausing, resuming, or archiving LinkedIn ad objects, but does not explicitly compare with alternative tools or provide when-not-to-use scenarios. Some guidance is present via the specific actions listed.

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