draft_create_rich_media_ad_item

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It merely restates the tool's name ('Create a new draft rich media ad item') without revealing side effects, validation requirements, permissions, return values, or how drafts relate to the broader campaign lifecycle.

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 short sentence with no wasted words, but it is under-specified rather than truly informative. It is concise but lacks substance, earning a middle 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 the lack of annotations, no output schema, and a loosely-defined nested 'draft' object, the description is insufficient for a create operation. It does not explain the rich media ad item field structure, how to save/commit the draft, or how the draft differs from a live ad item.

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 describes both parameters with 100% coverage, so the baseline is 3. The tool description adds no parameter-level detail, and the nested 'draft' object is only loosely described as containing rich media ad item fields with name required.

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 verb ('Create') and the resource ('new draft rich media ad item'), making the tool's purpose unambiguous. It also distinguishes from sibling draft tools for other ad item types (e.g., draft_create_image_ad_item) and from the non-draft create_rich_media_ad_item.

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 over alternatives, such as draft_create_image_ad_item or create_rich_media_ad_item. It doesn't explain the draft workflow, prerequisites, or whether this is for a draft campaign vs. a published campaign.

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