create_native_ad_item

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

No annotations are present, so the description carries full burden for behavioral disclosure. It does not mention permissions, whether this is a final vs. draft creation, side effects, or that it requires an existing native template. This is a minimal statement for a creation 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 sentence that front-loads the verb and object. Every word earns its place with no redundancy or filler.

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?

For a tool with 10 parameters, nested objects, no output schema, and a sibling draft variant, this description is too minimal. It lacks prerequisites (e.g., template must exist), variable matching expectations, and any context about how it fits into the ad item workflow.

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 detailed descriptions for all parameters, so the baseline is 3. The description's 'using a native template' adds no new parameter semantics beyond what the schema already states for the template field.

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 uses the specific verb 'Create' with a clear direct object 'new native ad item' and specifies the mechanism 'using a native template'. This distinguishes it from sibling tools like update_native_ad_item or draft_create_native_ad_item, which are clearly different operations.

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 phrase 'using a native template' implies this is the template-based creation path, but there is no explicit guidance on when to choose this over draft_create_native_ad_item or other create variants. No alternatives are named.

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