draft_create_custom_html_ad_item

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

With no annotations provided, the description carries the full burden but only repeats the action 'Create a new draft custom HTML ad item'. It does not disclose side effects, requirements, draft semantics, or any behavioral traits beyond the name itself.

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 concise sentence with no redundant words. It is appropriately front-loaded with the action, though it could have included more operational detail without becoming verbose.

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 the moderate complexity of two parameters and a nested object, the one-line description is insufficient. It lacks context about the draft lifecycle, the distinction from live ad items, and the expected outcome, making it incomplete for an agent to confidently invoke.

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 provides complete descriptions for both parameters (campaign_draft_id and draft), with 100% schema_description_coverage. The description adds no extra parameter context, so the baseline of 3 is appropriate.

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 states 'Create a new draft custom HTML ad item' with a specific verb (Create) and resource (draft custom HTML ad item). It clearly differentiates from siblings like draft_create_image_ad_item and create_custom_html_ad_item by including both 'draft' and 'custom HTML'.

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 provides no guidance on when to use this tool vs alternatives. It does not mention that this is for draft campaigns, that it should be used instead of create_custom_html_ad_item for non-draft items, or any exclusions.

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