yd_ad_extensions_delete

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 'Delete ad extensions.' without mentioning any behavioral traits such as destructive consequences, required permissions, reversibility, or side effects. This is insufficient for safe invocation.

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 clarity and completeness. It is under-specified and does not earn its place by providing enough information; it is more terse than 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 tool's destructive nature, the absence of annotations and output schema, and the low schema coverage (50%), the description is severely incomplete. It fails to explain return values, success/error handling, or how to use the optional client_login parameter, making it inadequate 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 covers 50% of parameters (description for client_login), but the description adds no extra meaning beyond the schema. The critical 'ids' parameter lacks explanation of what IDs refer to (e.g., ad extension IDs) or how to obtain them, leaving the agent with incomplete understanding.

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 ad extensions.' clearly states the action and resource, and among siblings like yd_ad_extensions_add and yd_ad_extensions_get, it distinguishes itself as the delete operation. However, it lacks specificity about what constitutes 'ad extensions' (e.g., types like sitelinks or callouts), which could cause ambiguity.

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 (e.g., yd_sitelinks_delete, yd_ad_images_delete). The context is implied by the name, but there are no explicit when-to-use or when-not-to-use instructions, making it difficult for an agent to choose correctly.

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