list_custom_html_ad_items

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

There are no annotations provided, so the description must fully disclose behavior. It only states 'List all custom HTML ad items' with no information about filtering, pagination behavior, whether archived or draft items are included, or any read-only guarantees. The response format is also not 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 sentence, extremely concise with no wasted words. It effectively communicates the core purpose without redundancy.

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?

With no output schema and no annotations, the description carries the full burden. It only states the basic purpose and relies on the schema for pagination, but fails to describe the return structure, any default behavior (e.g., including all items vs. paginated), or scope (e.g., all in the account vs. specific campaign). For a simple list tool, this is minimal but lacks useful context like whether it returns archived or draft items.

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 covers both parameters (limit and offset) with descriptions, giving 100% schema coverage. The description adds no additional parameter context, but the schema provides sufficient meaning, so the baseline score 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 'List all custom HTML ad items' clearly identifies the action (list) and the resource type (custom HTML ad items), which distinguishes it from list tools for other ad item types like list_image_ad_items. However, it does not explicitly state whether this is the non-draft/live version, which is a minor ambiguity given the existence of draft_list_custom_html_ad_items.

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 about when to use this tool versus alternatives such as list_ad_items (which may include all types) or draft_list_custom_html_ad_items. The description lacks any comparison or context to help the agent choose the correct list tool.

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