draft_create_native_ad_item

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

With no annotations available, the description must carry the full burden of behavioral disclosure. It merely states the action without explaining what 'draft' means (e.g., the item is not live until saved), potential side effects, or whether the operation is reversible. 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, concise, front-loaded sentence with zero wasted words. It efficiently communicates the core action and object, making it easy to scan.

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?

There is no output schema and no annotations, so the description should provide more context about what a 'draft' creation entails, what the tool returns (e.g., the created draft's ID), and how it fits into the broader draft/save workflow. The current description leaves these gaps unaddressed, making it incomplete for a tool with a nested object parameter.

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%, with clear descriptions for both 'campaign_draft_id' and 'draft'. The tool description adds no additional parameter semantics beyond what the schema already provides, 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 'Create a new draft native ad item' uses a specific verb ('Create') and clearly identifies the resource ('draft native ad item'), making it distinct from siblings like 'draft_create_catalog_ad_item' or 'create_native_ad_item'. The word 'draft' immediately signals a specific workflow context.

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 tool versus alternatives such as the non-draft 'create_native_ad_item' or the sibling 'draft_update_native_ad_item'. It does not explain the draft workflow or any prerequisites like the existence of a campaign_draft_id.

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