google_ads_get_user_list_details

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

No annotations are provided. The description only says 'Get detailed information' without disclosing behavioral traits such as required permissions, rate limits, or whether the user list must exist. It adds minimal context beyond the obvious read operation.

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 very concise: a clear single-line purpose, then structured args/returns/example. Every sentence adds value, and the 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 tool's simplicity (2 params, no nested objects, output schema exists), the description adequately explains parameters and gives an example. It does not detail the return structure, but the output schema compensates. Slight improvement would be mentioning the return content briefly.

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?

The schema has 0% description coverage, but the description adds meaning by specifying 'Customer ID (without hyphens)' and 'User list ID', and provides an example. This clarifies the expected format beyond the schema's type-only definitions.

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 'Get detailed information about a specific user list.' It uses a specific verb ('Get') and resource ('user list details'), and distinguishes from siblings like google_ads_list_user_lists (list all) and google_ads_create_user_list (create).

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 explicit guidance on when to use this tool versus alternatives like google_ads_list_user_lists. The implied usage is for retrieving details of a single user list given an ID, but the description does not explicitly state when to prefer this over listing or other actions.

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