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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no pagination, no return volume, no note on whether report_start_time/report_end_time narrow the results, and no clarification of what the 'GraphQL adgroup_targetedkeywords' reference implies for output shape. 'List' at least signals a non-mutating read, but that is the only behavioral cue.

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?

A single front-loaded sentence with the target resource stated first and no filler. The parenthetical GraphQL name is of marginal value to an agent but is short enough not to be wasteful.

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?

With six parameters, no annotations, and no output schema, the description does very little: it never states that campaign_id is required alongside ad_group_id, what the returned keyword records contain, or why a reporting date range would be passed to a keyword listing. For a tool of this shape the one-line description leaves significant gaps.

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 100%, so all six parameters (including campaign_id, ad_group_id, date range, adam_id, notification_message) are already documented in the schema; the baseline of 3 applies. The description adds no meaning beyond the schema, and notably does not explain how the optional date range interacts with a keyword listing.

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?

States a specific verb and resource ('List targeting keywords') plus the scope ('for an ad group'), which is enough to distinguish it from add_targeting_keywords and delete_targeting_keyword by the verb alone. It stops short of naming those siblings or clarifying what kind of keywords are returned (positive vs negative), so it is clear but not fully differentiated.

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?

There is no explicit guidance on when to use this versus the sibling list/add/update/delete keyword tools, nor any prerequisites such as needing an existing ad group. Usage is only implied by the verb 'List' and the scope 'for an ad group'.

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