create_sd_ad_groups

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

No annotations are provided, so the description must carry full weight. It mentions 'guarded write' and that the local stdio server is an 'introspection stub,' which is transparent about limited functionality. However, it does not detail side effects, permissions, or error behaviors for a full write operation.

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 brief (two sentences), front-loaded with the core action, and avoids extraneous details. The bracket prefix '[Ads / guarded write]' is slightly cryptic but not overly harmful; overall, each sentence earns its place.

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?

Without an output schema or annotations, the description should explain what the tool returns or effects. It only says 'preview or create' but gives no indication of output format, success indicators, or post-creation state. For a mutable tool, this is insufficient.

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 the schema already documents all five parameters. The tool description adds no further semantic value beyond restating the purpose; baseline score of 3 is appropriate.

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 explicitly states 'Preview or create Sponsored Display ad groups,' providing a clear verb and resource. It distinguishes from sibling tools like archive_sd_ad_groups by mentioning both preview and creation, and notes its hosted endpoint nature, avoiding ambiguity.

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 this tool is for previewing or creating ad groups, but does not explicitly state when to use it vs alternatives like create_sd_campaigns or archive operations. No 'when-not' or alternative tool names are provided, leaving usage context somewhat implicit.

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