add_keywords

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

With no annotations, the description carries the full burden. It explicitly discloses the dry-run behavior and preview, which is a critical safety trait. It also indicates that confirm=True executes. This is valuable, though it doesn't elaborate on the preview contents or other side effects.

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 exactly two sentences, with the purpose front-loaded and the safety behavior in the second sentence. No wasted words.

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 rich input schema and the presence of an output schema, the description is adequate. It explains the critical dry-run mechanism, and the schema covers parameters. It does not need to explain return values due to the output schema, but it could mention permissions or preview contents; still, it is sufficiently complete for this tool.

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 input schema already provides detailed descriptions for all five parameters, including the keywords dict structure. The description adds no additional parameter-level information beyond what the schema states, so it does not exceed the baseline for high schema coverage.

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 clear action: 'Add keywords to an ad group.' This is specific about the resource (keywords) and target (ad group), and the tool name distinguishes it from siblings like add_negative_keywords, even though the description doesn't explicitly name alternatives.

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 gives a clear execution guideline: 'Default is DRY RUN — shows preview. Pass confirm=True to execute.' However, it does not provide any guidance on when to use this tool versus alternatives such as add_negative_keywords or update_keyword_bid, so usage context is implied rather than explicit.

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