google_ads_campaigns_update

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

With no annotations, the description carries the burden and discloses that the operation is mutating and not automatically reversible, and suggests recording before-state for rollback. However, it does not detail required permissions or other side effects, so not a 5.

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?

Three sentences with no fluff. Each sentence adds unique value: action, partial update behavior, mutability warning, and alternative tool recommendation. Information 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 4 parameters, no output schema, and no annotations, the description sufficiently covers return value, partial update behavior, rollback guidance, and alternative usage. It is complete enough for an agent to select and invoke correctly.

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 baseline is 3. The description adds valuable partial-update semantics—only fields provided are changed, omitted fields are preserved—which clarifies how all parameters behave beyond schema descriptions.

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 'Updates one or more settings on an existing campaign' with a specific verb and resource. It also differentiates from the sibling tool by explicitly noting that status-only changes should use google_ads_campaigns_update_status instead.

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?

Provides explicit usage guidance: for status-only changes, prefer the lighter-weight google_ads_campaigns_update_status. Also explains partial update semantics, giving the agent context on when to use this tool versus alternatives.

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