delete_custom_html_ad_item

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

No annotations are provided, so the description must disclose behavioral traits. It simply says 'Delete' without mentioning whether the deletion is permanent, requires special permissions, or has cascading effects, offering no extra transparency.

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, grammatically complete sentence with no unnecessary words or repetition, making it very concise and easy 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 destructive operation, the description is minimal and omits important context such as the distinction between draft and live ad items, the permanence of the action, or any prerequisites. It is barely sufficient for such a tool.

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 schema fully documents the id parameter with 'Ad item ID', and since the description adds no parameter details, it relies on the high schema coverage. This meets the baseline for acceptable parameter semantics.

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 uses the specific verb 'Delete' and names the resource 'custom HTML ad item', clearly indicating the tool's function and distinguishing it from deletion tools for other item types. However, it doesn't clarify that this operates on the live (non-draft) version, leaving potential ambiguity with draft_delete_custom_html_ad_item.

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 draft_delete_custom_html_ad_item or other delete_* tools. It lacks any contextual information to help the agent choose it.

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