create_keyword

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'enabled by default', which is a behavioral trait, but fails to disclose that the tool is a mutation (creates a resource), that it supports a preview mode via the confirm parameter, or any required permissions or side effects. The description is insufficient for a mutation tool.

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 a single concise sentence, front-loaded with key information. However, it is overly brief, sacrificing important details like preview behavior and usage context. While efficient, it leaves gaps that force reliance on the schema.

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 6 parameters (3 required) and an output schema, the description is incomplete. It does not explain the preview behavior controlled by confirm, the expected return value (despite output schema existing), or the relationship between keyword_text and other parameters. The description is too minimal for the tool's complexity and the lack of annotations.

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%, meaning all parameters have descriptions in the input schema. The tool description itself adds no additional meaning beyond the schema, such as clarifying the relationship between parameters or providing usage examples. The description's note about 'enabled by default' refers to the created keyword's state but does not explain any parameter directly. Baseline 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?

The description clearly states the verb 'Create' and resource 'keyword', with a note that it's enabled by default. It distinguishes from sibling tools like enable_keyword, pause_keyword, update_keyword_bid, and get_keywords. However, it does not explicitly mention that the keyword is attached to an ad group, though the schema makes that clear.

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. There is no mention of prerequisites, when to use preview mode (confirm parameter), or comparison to other creation tools like create_ad_group or create_campaign. The description lacks any context for appropriate usage.

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