draft_list_image_ad_items

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 says 'List all' without noting that results are paginated (despite limit/offset parameters), what the return format is, or that it is a read-only operation. The word 'all' may mislead an agent into expecting all results in one response.

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 sentence with no filler. It is front-loaded and immediately conveys the core action and resource, making it easy for an agent to parse.

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 simple list tool with only pagination parameters and no output schema, the description is minimally viable. However, it omits details about pagination behavior, the meaning of 'draft' in this context, and does not differentiate from the non-draft counterpart, leaving some ambiguity.

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 thoroughly describes both limit and offset parameters (100% coverage). The description adds no extra meaning about the parameters, so this dimension is at the baseline.

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 action (List) and the resource (draft image ad items), and the scope is indicated by 'all'. It distinguishes from siblings like list_image_ad_items and draft_list_ad_items by combining the draft status and image type, though it does not explicitly mention the distinction.

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 such as list_image_ad_items (non-draft) or draft_list_ad_items (all types). There is no mention of exclusions, prerequisites, or when other tools would be more appropriate.

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