google_ads_create_user_list

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

No annotations exist, so the description must cover behavioral traits. It details the creation operation, URL pattern logic, membership duration range, and a prerequisite. It does not mention permissions or rate limits, but provides key constraints.

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 well-structured: purpose, types, args with details, return info, example, and note. Every sentence adds value without redundancy, and key information is front-loaded.

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 output schema exists, the description appropriately includes return details ('Success message with user list ID'). All parameters are covered, and the note about remarketing tags addresses prerequisites. The example enhances 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 description coverage is 0%, but the tool's description compensates fully. Every parameter is explained with examples, defaults, and format requirements (e.g., customer_id without hyphens, url_contains OR logic). An example call further clarifies usage.

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 tool's purpose ('Create a remarketing user list'), lists types like CRMBASED and RULE_BASED, and provides an example. It distinguishes from sibling tools focused on listing or uploading audiences.

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 explains when to use each list type and includes a note about RULE_BASED lists requiring remarketing tags. However, it does not explicitly compare with sibling tools like google_ads_upload_customer_match or google_ads_add_audience_to_ad_group.

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