draft_create_catalog_ad_item

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 does not explain side effects, whether a draft campaign must exist first, whether creation is reversible, or what happens to the draft after creation. The description simply restates the creation action without adding context.

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 with no redundant words. It is front-loaded with the action and resource, and every word contributes to the meaning. This is appropriately concise.

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 no annotations, no output schema, and a nested object parameter, the description is too minimal. It lacks context about the draft workflow, prerequisites (e.g., the need for a campaign_draft_id), or what a successful creation returns. The schema covers parameter meanings, but broader context is missing.

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 100%, so parameters are already fully documented in the schema. The description adds no additional parameter semantics beyond what the schema states, thus meeting the baseline for schema-covered tools.

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 ('Create a new') and the resource ('draft catalog ad item'), using a specific verb and noun combination. It distinguishes itself from siblings like 'create_catalog_ad_item' through the 'draft' qualifier, leaving no ambiguity about what it creates.

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 about when to use this tool vs. alternatives such as 'create_catalog_ad_item' or 'campaign_bulk_create_catalog_ad_items'. The 'draft' prefix implies usage in a draft workflow, but this is not explicitly stated, and no alternatives or exclusions are mentioned.

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