Удалить группы объявлений

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

Annotations already flag destructiveHint=true, but the description adds specific context: it deletes ads and key phrases along with the group, and explicitly states that this cannot be undone. This goes beyond the annotation flags and fully discloses the behavior's consequences.

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, tight sentence that front-loads the action and immediately provides the cascade and irreversibility caveats. There is no filler or redundancy, 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 destructive tool with one parameter and no output schema, the description covers the action, endpoint, destructive scope, and irreversibility completely. Nothing an agent needs to call it correctly is missing.

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 already fully documents the single 'ids' parameter with a description ('Id групп, которые нужно удалить'), so the description adds no additional semantic depth. With 100% schema coverage, the baseline of 3 applies as the description does not compensate with extra parameter details.

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 states a specific verb ('Удаляет' – deletes) with a clear resource ('группы объявлений' – ad groups) by id, and references the API endpoint. It distinguishes from siblings like update_ad_group and list_ad_groups by its destructive scope, and explicitly notes it removes associated ads and key phrases.

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 clearly implies when to use it (when permanently deleting ad groups) and warns about the cascade deletion, which helps disambiguate from tools like ad_action or keyword_action. However, it does not explicitly name alternative tools or state conditions when not to use it, so it stops short of full routing guidance.

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