Submit Bulk Mutation Job

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

With no annotations, the description carries the behavioral burden. It discloses that the operation is asynchronous and mentions entity linking via idempotency keys, which is useful. However, it does not describe expected job result, polling/status-checking behavior, side effects, or error behavior.

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 sentences with no filler; the core behavioral trait (asynchronous bulk submission) and key parameters are front-loaded. Every clause adds useful information.

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?

For a complex async bulk mutation tool with no output schema and no annotations, the description gives enough to invoke correctly but omits what the response looks like and how to track the job. The schema covers parameters, but the missing status/return guidance leaves a meaningful gap.

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?

The schema already provides 100% parameter coverage, establishing a baseline of 3. The description adds extra meaning by explaining that entities can be linked via campaign_idempotency_key and ad_group_idempotency_key, which is not explicitly in the schema properties and clarifies how operations relate.

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 uses a specific verb ('submits') and resource ('asynchronous bulk job') and specifies the exact operation types and the 1,000-operation limit. It clearly distinguishes itself from sibling tools like get_bulk_mutation_job_status and individual create/update endpoints.

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 use for bulk operations by noting the asynchronous job nature and the up-to-1,000-operation capacity. However, it does not explicitly say when to prefer this over individual mutation tools, nor does it name alternatives or exclusions.

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