yd_retargeting_lists_delete

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

With no annotations provided, the description must fully disclose behavioral traits. It merely states 'Delete', implying a destructive action, but fails to describe the scope of deletion (e.g., permanent removal), required permissions, or any side effects. This is insufficient for safe usage.

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 extremely concise at one sentence, but it sacrifices essential information for brevity. While it is front-loaded, it does not earn its place because it omits critical details about parameters and usage. A slightly longer description would be more helpful.

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?

Given the lack of output schema and parameters with incomplete descriptions, the tool description is incomplete. It does not explain the outcome of deletion, error handling, or any return values. For a delete operation, such context is necessary for correct 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?

The input schema has 50% description coverage, with 'ids' lacking any description. The tool description does not add any meaning beyond the schema; it does not explain what 'ids' represent (list identifiers) or how the optional 'client_login' parameter affects behavior. No additional parameter semantics are provided.

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 'Delete retargeting lists' clearly states the verb (delete) and the resource (retargeting lists), making the primary action obvious. However, it does not provide any additional context to differentiate from sibling tools like get or add, which is acceptable given the name already implies deletion.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites, such as the need to ensure lists exist or that deletion is irreversible. This leaves the agent without guidance on appropriate contexts.

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