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 of behavioral disclosure. It only states 'Create a new custom HTML ad item', which adds nothing beyond the action itself. It does not mention permissions, validation, side effects, error behavior, or any operational nuances. This is a severe 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, compact sentence that directly states the action. It is front-loaded and contains no verbose or redundant words. It earns its place by providing a minimal purpose statement, though it is quite terse and almost paraphrases the tool 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?

This tool has 12 parameters, 2 required, enums, and nested objects, yet the description is only one sentence. There is no output schema or annotations to compensate. The description fails to provide any context about the ad item's structure, required fields, or how it relates to sibling ad item creation tools. It is fundamentally inadequate for a tool of this complexity.

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 has 100% description coverage for all 12 parameters, so the schema itself fully documents each parameter's meaning. The description adds no parameter-level details, but since coverage is high, the baseline of 3 is appropriate. The description does not clarify relationships between parameters or any special semantics beyond the schema.

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 'Create a new custom HTML ad item', which includes a specific verb ('create') and resource ('custom HTML ad item'). It is unambiguous in its basic purpose. However, it does not distinguish itself from sibling tools like draft_create_custom_html_ad_item or other ad creation tools (create_image_ad_item), so it lacks explicit differentiation.

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 versus alternatives. It does not mention that this creates a published/custom HTML ad item as opposed to a draft, nor does it reference sibling tools like draft_create_custom_html_ad_item or other ad item creators. There is no context about prerequisites or suitable scenarios.

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