google_ads_create_shopping_campaign

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

Without annotations, the description provides some behavioral context (e.g., priority affects bidding), but lacks information on creation behavior (e.g., whether the campaign is paused by default, or if it overwrites existing campaigns). No details on authentication or rate limits.

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 well-structured, starting with the core purpose, then a brief explanation, followed by a clear Args list, Returns, and an example. Every sentence adds value without redundancy.

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 7 parameters and no annotations, the description covers the tool's purpose and parameter meanings adequately. It could add context about the campaign's initial status or prerequisites (e.g., Merchant Center account required), but the example and return type provided are sufficient.

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?

With 0% schema description coverage, the description compensates fully by explaining each parameter, including formats (e.g., '10 digits, no hyphens'), defaults, and constraints (e.g., 'LOW, MEDIUM, HIGH' for priority). The example further clarifies usage.

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 'Create a Google Shopping campaign' and explains that Shopping campaigns promote products from Merchant Center, distinguishing it from other campaign types like App, Local, or Performance Max campaigns mentioned in sibling tool names.

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 promoting products via Google Shopping but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or alternative tool references are provided.

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