add_keywords

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

The description indicates mutation (adding), but lacks details on whether it appends or overwrites existing keywords, any limits, or required permissions. With no annotations, the description should have compensated.

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?

A single sentence with no redundancy. However, it could be more informative while remaining concise. The language mismatch (Russian vs English name) is a minor drawback.

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?

The tool is simple, but the description omits return behavior (e.g., success code, error messages) and side effects. This leaves the agent guessing about outcomes.

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%, so baseline is 3. The description adds no extra meaning beyond the schema's field descriptions; it repeats the same information without clarifying keyword format or constraints.

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 'add' and the resource 'key phrases to an ad group,' which distinctively sets it apart from sibling tools (e.g., list_keywords, create_ad_group). The translation 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?

No guidance is provided on when to use this tool versus alternatives. For instance, it does not mention that the ad group must exist first, nor does it differentiate its behavior from a hypothetical 'update_keywords' tool.

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