update_sd_ad_group_state

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

With no annotations, description carries full burden. It discloses the tool is a stub ('local stdio server is an introspection stub') and mentions 'guarded write'. However, it does not explain what guarded write entails or behavioral details like whether preview is non-destructive.

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?

Two sentences plus prefix, efficient and minimal. Every part adds context, though 'introspection stub' might be jargon.

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?

Lacks explanation of guarded write, expected response (no output schema), or specific state values. For a tool with 5 optional params, more detail on usage flow 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%, baseline is 3. Description adds value by linking 'preview' and 'dry_run' boolean to the preview behavior, but does not clarify the 'changes' array structure or required fields for state transitions.

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?

Description clearly states the tool operates on Sponsored Display ad groups with actions 'Preview or set' state. The prefix '[Ads / guarded write]' and explicit resource differentiation from siblings like update_sb_ad_group_state provide strong purpose clarity.

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?

No guidance on when to use preview vs set, or when to choose this tool over alternatives. The mention of 'Hosted endpoint only' hints at limitations but does not provide explicit usage context or exclusions.

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