create_sb_ad_groups

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

With no annotations, the description must disclose behavior. It states the tool can 'preview' or 'create', and labels it as 'guarded write', implying safeguards. However, it does not explain what 'guarded write' entails, what happens to existing data, or what the response looks like. The behavioral details are present but insufficiently detailed.

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 two sentences long, front-loads the purpose, and contains no redundant information. Every phrase serves a purpose: indicating the tool's action, scope, and limitations. Highly efficient.

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 tool has 5 parameters and no output schema, yet the description does not mention what the tool returns (e.g., the created ad group ID or preview results). It lacks context on error handling, idempotency, or the effect of setting both preview and dry_run. The description is too sparse given the tool's complexity and missing output schema.

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 baseline is 3. The description adds little beyond what the schema already provides: 'Preview or create' aligns with the 'preview' and 'dry_run' parameters, and 'changes' is described as 'high-level desired changes'. No additional value beyond schema.

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 'create Sponsored Brands ad groups', which is a specific verb+resource combination. It also mentions 'Preview or create', clarifying the dual capabilities. The tool is clearly distinguished from siblings like 'create_sp_ad_groups' by specifying 'Sponsored Brands'.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention when-not-to-use, prerequisites, or comparisons with sibling tools like 'create_sp_ad_groups' or 'archive_sb_ad_groups'. The note about 'Hosted endpoint only' is informative but not a usage guideline.

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