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

Annotations already disclose destructiveHint=true and openWorldHint=true, so the safety bar is lower. The description adds some useful context by listing statuses such as ACTIVE, PAUSED, and ARCHIVED, but it does not explain the consequences of ARCHIVED or how validate_only behaves.

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 compact and front-loads the operation and updatable fields. The trailing ellipsis after ARCHIVED slightly weakens precision.

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?

The output schema exists, so return values need not be described. However, the description leaves out the dry-run validate_only parameter and does not clarify the destructive effect of archiving, which matters for a mutation tool annotated destructiveHint=true.

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 0%, so the description must compensate. It documents name, status values, and the workspace slug semantics, but omits two important parameters: validate_only and campaign_group_id.

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 names the exact resource and operation: updating a LinkedIn campaign group's name and/or status. It is clearly distinct from linkedin_create_campaign_group and linkedin_list_campaign_groups, but it does not explicitly contrast itself with those siblings.

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 explains which fields can be changed but gives no guidance on when to use this tool instead of creating a new group or updating related campaign entities. It also does not mention prerequisites, safety checks, or when not to use it.

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