list_image_ad_items

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

With no annotations, the description carries the full burden of behavioral disclosure. It merely repeats the tool's purpose and adds no information about pagination, whether archived/draft items are included, required permissions, or the nature of 'all'. The word 'all' is ambiguous given the presence of limit/offset parameters in the schema, and no side effects are mentioned.

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, achieving high conciseness. However, it is arguably under-specified for a tool with pagination and many siblings, so it is not a perfect 5.

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 tool is simple with only two well-documented parameters, but the description fails to provide sufficient context for an agent to understand when to choose this tool over list_ad_items or draft_list_image_ad_items. It also does not explain what an 'image ad item' is or what the response contains, leaving the description incomplete for effective selection and invocation.

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% for the two parameters (limit and offset), so the baseline is 3. The description's phrase 'all' hints at unbounded listing but does not add any meaningful detail beyond the schema's own parameter descriptions.

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 'List all image ad items' clearly specifies the action (list) and the resource (image ad items), distinguishing it from sibling tools for other ad item types. However, it adds little beyond the tool name itself and does not clarify the intended scope (e.g., all items across all advertisers or within a 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?

The description provides no guidance on when to use this tool versus alternatives, no exclusions, and no mention of related tools like draft_list_image_ad_items for draft versions. It is a bare functional statement with zero usage context.

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