Ads batch submit

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

Annotations only declare the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true); the description adds genuinely non-obvious behavior — execution is asynchronous and returns a BatchJob tracked through a separate call. It omits any mention of the optional 'confirm' gate and of failure/partial-failure semantics for a mutating bulk 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?

A single sentence with the scale constraint and async behavior front-loaded, and the follow-up tool routing at the end. No filler or restatement of the name.

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?

An output schema exists, so return values need not be explained, and the async/tracking model is covered. However, for a three-parameter bulk mutation with zero schema documentation, the unexplained 'confirm' parameter and the lack of guidance versus ads.mutate leave meaningful gaps.

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 0%, so the description must carry parameter meaning, but it only conveys that 'operations' is a large array of MutateOperations. 'customer_id' and especially 'confirm' (which defaults to null and is presumably a safety gate) are left completely undefined in both schema and description.

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 ('Submit') plus resource ('a large mutation ... as an asynchronous BatchJob') and a scale qualifier ('thousands of MutateOperations'). It implicitly separates itself from the synchronous ads.mutate sibling by emphasizing scale and async execution, though it never names that sibling.

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?

Gives a usable selection threshold (large mutations measured in thousands of operations) and points to ads.batch.status for tracking. It stops short of an explicit exclusion such as 'use ads.mutate instead for small synchronous changes', so the when-not half is left to inference.

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