Удалить быстрые ссылки

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. Beyond that, the description discloses a concrete behavioral guardrail — that Direct will refuse to delete a sitelink set bound to an ad — which is genuine value not present in the annotations or schema.

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?

Two short sentences, front-loaded with the action and resource, followed immediately by the key constraint. No filler.

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 single-parameter destructive tool with no output schema and annotations covering the safety profile, the description is almost complete: it names the resource, the identifier source, and the one behavioral gotcha. It lacks only a note on the outcome/error behavior when deletion is blocked.

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% and the single array parameter is fully documented ('ID набора быстрых ссылок', sourced from list_sitelinks). The description adds nothing beyond what the schema already conveys, so the baseline of 3 applies.

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?

States a specific verb and resource ('Удалить наборы быстрых ссылок по ID' / delete sitelink sets by ID), which an agent can distinguish from the sibling set_sitelinks (create/attach) and list_sitelinks (read). The scope is unambiguous.

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 adds a useful contextual condition ('a set attached to an ad cannot be deleted'), which implicitly hints at a precondition, but it never states when to prefer this tool over alternatives or how to resolve the blocked-deletion case (e.g., unlink first). Usage is implied rather than guided.

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