Удалить наборы быстрых ссылок

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

Annotations already indicate destructive behavior and non-idempotency. The description adds a meaningful behavioral constraint: deletion only succeeds for sets not attached to any ad. It does not contradict annotations, though it could disclose behavior when some IDs are linked or invalid.

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 sentence with no filler. It front-loads the action and resource, then immediately states the critical constraint in a parenthetical. Every part contributes to correct invocation.

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 simple one-parameter delete operation with annotations covering destructive behavior, the description is largely complete. It does not describe the response or error handling if some ids are linked to ads, but the core constraints and action are clear. Given there is no output schema, a bit more detail could help, but the definition is adequate for safe 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 schema already fully describes the 'ids' parameter with 100% coverage. The description mostly restates that deletion happens by id and adds the unlinked constraint, which is behavioral rather than parameter-specific. Since the schema carries the parameter meaning, a baseline score of 3 is appropriate.

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 clearly states the action ('Удаляет' — deletes) and the resource ('наборы быстрых ссылок' — sitelink sets), and specifies deletion by id. It also distinguishes itself from other deletion tools like delete_callouts or delete_ad_groups by targeting sitelink sets specifically.

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 implies this tool is for deleting sitelink sets and adds the important condition that only unlinked sets can be deleted. However, it does not explicitly state when to prefer this over create_sitelinks_set or get_sitelinks, nor does it mention alternatives or exclusions beyond the unlinked requirement.

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