Launch Google Search

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

Annotations only carry readOnlyHint=false, so the description shoulders most of the burden and does add real value: it discloses that the campaign launches in a paused state and requires confirming a preview. That is meaningful safety/flow context beyond the annotation. It still omits auth requirements and what the launch actually returns or triggers.

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 tight sentences with zero waste. The core action is front-loaded and the behavioral caveat (starts paused, preview confirmation) follows immediately.

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?

With no output schema and minimal annotations, the description covers purpose and the key behavioral quirk (paused launch, preview confirmation). The main gap is that the empty input schema leaves the keyword/ad-text handoff unexplained, but for a launch action this is close to complete.

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?

There are zero schema parameters, so the baseline is 4. The description references 'your keywords and ad text,' which hints at required inputs, but since the schema is empty with additionalProperties=true it does not clarify how those inputs are supplied or their format.

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?

Specific verb (launch) plus channel-specific resource (Google Search campaign), which cleanly separates it from launch_meta_ad, launch_tiktok_campaign, and launch_pmax_campaign. It also states the required inputs qualitatively (keywords and ad text). It stops short of explaining how it relates to the generic launch_campaign sibling, so a 4 rather than a 5.

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 gives process context ('starts paused, after you confirm a preview') but never states when to choose this tool over launch_campaign, launch_pmax_campaign, or the other launch_* siblings. Usage is implied by the channel name, but no explicit when/when-not guidance or prerequisites are provided.

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