draft_list_native_ad_items

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

No annotations are provided, and the description only restates the tool's purpose without adding behavioral details such as pagination behavior, result ordering, or whether the list is scoped to a specific advertiser. The statement 'List all draft native ad items' adds no information beyond the tool's name.

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 filler words. It is appropriately brief for a simple list operation, though it could include more context without becoming wordy.

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?

The description is very minimal and does not clarify important context such as whether 'all' means across the entire account, how pagination works, or how this tool differs from siblings like list_native_ad_items and draft_list_ad_items. Given the large sibling set, this lack of context is a significant gap.

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% coverage with descriptions for both 'limit' and 'offset', so the baseline is 3. The tool description does not add any parameter information, but the schema already fully documents the parameters.

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 a specific verb ('List') and resource ('draft native ad items'). It also includes the scope 'all' which distinguishes it from sibling tools like list_native_ad_items (likely non-draft) and draft_list_ad_items (all ad item types).

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. It does not mention that list_native_ad_items exists for live items or draft_list_ad_items for all types, nor does it state any exclusions or preferred usage context.

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