draft_keywords

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

Annotations (readOnlyHint: false, destructiveHint: false) are basic. Description adds crucial behavior: returns a PREVIEW, does NOT add keywords, requires confirm_and_apply. Discloses the two-step process and non-destructive nature.

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 sentences, front-loaded with purpose. Every sentence adds value: first states what it does, second details keyword format and follow-up action. 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?

Covers the main behavior, return value (plan_id), and required follow-up tool. Could have explained optional customer_id parameter, but overall complete given the tool's simplicity and presence of output schema.

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 0%. Description only explains the 'keywords' parameter format with examples, but does not clarify 'ad_group_id' or 'customer_id'. Partially compensates for lack of schema descriptions.

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?

Clearly states action ('draft') and resource ('keyword additions'), explicitly says it returns a preview and does NOT add keywords. Distinguishes from sibling tools like 'add_negative_keywords' by indicating it's a preparatory step.

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?

Provides explicit instruction to call confirm_and_apply to execute, and specifies that it does not add keywords. However, it doesn't elaborate on when to use this tool versus other sibling tools beyond the follow-up step.

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