google_ads_add_keywords

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the tool adds keywords and returns a success message with a count, but does not detail side effects like duplicate handling, overwrite behavior, or permission requirements. Transparency is adequate but not thorough.

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 front-loaded with the main purpose and includes structured arg descriptions and an example. It is reasonably concise, though the example could be trimmed. Each sentence adds value without redundancy.

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 tool's moderate complexity and presence of an output schema (not shown), the description covers the inputs well and indicates the return type. It lacks details on error handling or batch size limits, but is largely complete for the intended functionality.

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 description significantly enhances the input schema by specifying format details (customer_id without hyphens), required fields for keyword objects (text and match_type), and allowed values for match_type (EXACT, PHRASE, BROAD). It also clarifies the cpc_bid as optional and in currency units. With 0% schema description coverage, the description fully compensates.

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 'Add keywords to an ad group' with a specific verb and resource. It provides an example with keyword match types, making the action unambiguous. However, it does not differentiate from siblings like google_ads_batch_add_keywords or google_ads_bulk_add_keywords, so the purpose is clear but not fully distinguished from similar 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 provides no guidance on when to use this tool versus alternatives such as batch or bulk versions. It does not mention prerequisites, limitations, or context for use, leaving the agent to infer appropriate usage.

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