create_sb_ads

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

With no annotations, the description provides key behavioral traits: 'guarded write' indicates safety mechanisms, and the note that this local server is an introspection stub for a hosted endpoint explains that it's not fully functional locally. This adds useful context beyond the basic function.

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, concise and front-loaded with the main purpose. However, the second sentence is somewhat cryptic and could be clearer about the stub nature.

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 the tool has 5 parameters and no output schema, the description adequately states the purpose and guard mechanism but lacks details on expected output or how to distinguish preview versus create behavior. The sibling context is provided but not leveraged in the description.

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 no parameter-specific details beyond what the schema provides; it only mentions 'caller-supplied creative' and 'preview or create' at a high level.

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 the tool is for previewing or creating Sponsored Brands ads with caller-supplied creative. It differentiates from siblings by mentioning 'guarded write' and that it's a hosted endpoint stub, though it doesn't explicitly contrast with other create tools like create_sb_ad_groups.

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 usage for previewing or creating SB ads but does not explicitly state when to use this tool versus alternatives (e.g., when to preview vs create, or vs archive tools). No exclusions or prerequisites are given.

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