add_keywords

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

Description states 'Add keywords', consistent with destructiveHint annotation. No additional behavioral context beyond the annotation. Since annotations already flag destructive behavior, description does not need to repeat but could add value on side effects like cost impact.

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?

Single sentence, no wasted words. Information is front-loaded. Appropriate for a simple tool.

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?

No output schema and description does not explain return values or error conditions. For a mutation tool (destructiveHint), agent needs to know what to expect after execution. Missing this context reduces completeness.

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 all parameters have descriptions. The description adds no extra nuance beyond what the schema provides. Baseline score of 3 is appropriate.

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 adding keywords to Google Ads. Verb and resource are specific. However, description mentions both campaign and ad group, but input schema only requires ad_group_id, slightly inaccurate. Distinguishes from sibling 'add_negative_keywords' by implication.

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 on when to use this tool versus alternatives like add_negative_keywords. No context on prerequisites or exclusion criteria. Agent must infer from name alone.

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