campaign_bulk_create_catalog_ad_items

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It simply says 'bulk create', which implies a write operation, but does not disclose whether the operation is atomic, what happens on partial failures, whether there are rate limits, or any validation requirements. This is a significant gap for a mutation tool.

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 a single sentence that is concise and front-loaded with the key action. However, it is almost too terse, omitting any additional useful context that could be included without becoming verbose. It does not waste words, so it earns a slightly above-average score.

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 that there are no annotations, no output schema, and the items array parameter is loosely defined (additionalProperties: {}), the description is insufficiently complete. It does not explain what fields are expected in each item, how many items can be submitted, or the response/error format. The context of sibling tools like create_catalog_ad_item and draft_create_catalog_ad_item suggests more detail is needed to use this tool correctly.

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 input schema already provides descriptions for both parameters (campaign_id and items), so schema coverage is 100%. The description does not add any extra meaning beyond the schema, such as constraints on the items array structure or size limits. Since the schema handles the basics, a baseline of 3 is appropriate, but the description could have compensated for the vague item object definition.

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 action (bulk create), the resource (catalog ad items), and the scope (in a campaign). It is specific and distinguishes itself from the singular create_catalog_ad_item tool by using the word 'bulk', making the purpose unambiguous.

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?

No guidance is provided on when to use this bulk operation versus the singular create_catalog_ad_item or other related tools. There is no mention of preferred scenarios, limitations, or alternatives. The description only states the action without contextual guidance.

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