Управление объявлениями

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

Annotations already indicate destructive (destructiveHint: true). The description adds a critical behavioral detail: '⚠️ delete необратимо' (delete is irreversible). This provides valuable context beyond annotations. No other behavioral traits (e.g., auth needs, side effects) are described, but the warning is sufficient for a score of 4.

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 plus a warning, very concise. It is front-loaded with the action list. Minor improvement could be using a bullet list for clarity, but overall it is efficient and to the point.

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 moderate complexity (6 actions, no output schema), the description is adequate but lacks details on the effects of each action (e.g., what 'suspend' vs 'archive' does). It warns about delete but does not explain behavior for other actions. With 2 parameters and annotations, more completeness would be helpful.

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 coverage is 100% with parameter descriptions for both 'ad_ids' and 'action'. The description does not add new meaning to these parameters beyond listing the actions again. The baseline is 3 since schema already documents them.

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 verb 'manage' and resource 'ads', listing specific actions (suspend, resume, archive, etc.). This distinguishes it from sibling tools like 'delete_ad_groups' (different resource) and creation/edit tools.

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 lists available actions, implying when to use the tool (when performing actions on ads). However, it does not explicitly specify when not to use it or provide comparisons to alternative tools (e.g., 'delete_ad_groups' for ad groups; no alternative for deleting ads). No exclusions are given.

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