update_sd_campaign_state

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

No annotations are provided, so description carries full burden. Discloses guarded write and preview capability, but does not detail side effects, required permissions, rate limits, or consequences. The term 'guarded write' adds some safety context but insufficient for full transparency.

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?

Very concise: two sentences covering purpose and environment. Front-loaded with category and action. Efficient but could include slightly more detail on usage without becoming verbose.

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 no output schema and 5 parameters, the description is too minimal. It does not explain return values (e.g., preview results or success confirmation), error conditions, or prerequisites for the write operation. The stub note helps but leaves significant gaps for a tool that mutates state.

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 adequate parameter descriptions. The tool description adds no additional parameter context, so baseline score applies.

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?

Clearly states verb ('Preview or set') and resource ('Sponsored Display campaign state'). Differentiates from sibling tools targeting budget, ad groups, or other ad types (SB, SP) and from state updates on other entities.

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?

Mentions use cases: preview and set. Indicates it's a guarded write for Ads, and that it's a hosted endpoint (not a local stub). However, lacks explicit when-not-to-use or direct comparison to alternatives like other state-update tools.

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