draft_list_custom_html_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 states the obvious listing action and does not add context about pagination, default behavior, filtering, or whether it returns only draft items (though 'draft' is implied). No side effects or additional details are disclosed.

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 or redundant content. Every word contributes to clarity, making it highly efficient.

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 two parameters and no output schema, the description is minimally adequate. However, it lacks any context about behavior beyond the basic action, such as ordering, default limit application, or differences from the broader draft_list_ad_items tool, leaving some gaps for a fully self-sufficient description.

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 both 'limit' and 'offset' parameters having clear descriptions. The tool description adds no parameter-specific information, but the schema already documents syntax and defaults, meeting the baseline for high coverage.

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 draft custom HTML ad items' uses a specific verb (List) and resource (draft custom HTML ad items), making the primary action clear. It does not explicitly differentiate from similar sibling tools like 'draft_list_ad_items' or 'draft_list_rich_media_ad_items', but the resource type is well specified.

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. There is no mention of when to prefer this over draft_list_ad_items, draft_list_image_ad_items, or other draft list tools, nor any exclusions or prerequisites.

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