Create Keyword

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

With no annotations, the description carries the full burden for a mutation tool, yet it does not say what permissions are needed, whether creation is idempotent, what happens if some keywords already exist or fail, or whether any batch limit applies. It also never mentions confirm_token, which strongly implies a confirmation step the agent must handle.

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?

Two short sentences, front-loaded with the action and followed by the constraint that matters most for correctness. Nothing is padded, though the terseness comes at the cost of the missing guidance noted elsewhere.

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?

An output schema exists, so return values need no explanation, but the definition is still thin for a four-required-parameter bulk mutation with a confirmation token. An agent would have to guess at batch limits, duplicate handling, and the confirm_token workflow before calling it safely.

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 description coverage is 0% across five parameters, so the description must compensate. It adds real value by enumerating match_type values (EXACT, PHRASE, BROAD) since the schema declares no enum, but it says nothing about the texts array format, ad_group_id/customer_id sourcing, or what confirm_token is and how to obtain it.

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?

States a specific verb and resource ("Create several keywords") plus the scope ("in an ad group"), which separates it from add_negative_keyword and set_keyword_status in the sibling list. The plural "several" usefully signals a bulk operation, though it does not explicitly name the tools it replaces.

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?

There is no guidance on when to use this versus add_negative_keyword, set_keyword_status, or other creation tools, and no stated prerequisites such as campaign/ad group state or account permissions. The only usage signal is the implied one from the name and the match_type note.

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