List Do Not Reach lists

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

Annotations already establish read-only and open-world hints, so the description only needs to add behavioral context. It adds that an account has at most one DNR list, that it applies to ALL campaigns, and that it does not strip users from custom audiences – meaningful context beyond annotations.

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?

Three short sentences, front-loaded with the core concept and no filler. Each sentence adds distinct information: definition, cardinality, and scope/effect.

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?

The definition gives strong conceptual context but never states what the tool returns (the DNR list contents/metadata) or how count/cursor affect results. With no output schema, that missing return information is a real gap, though the operation is simple and read-only.

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 only 33%: only account_id has a description. The tool description mentions no parameters and does not explain count or cursor, so it fails to compensate for the low schema coverage.

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 title supplies the verb 'List' and the description identifies the resource as an account-level DNR (suppression) list. It explains scope and effect, which distinguishes it from audience tools, but the description itself never explicitly states that it retrieves/returns the list.

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 the DNR concept and its account-level behavior, which implies when an agent would want it. It does not explicitly name alternatives or state conditions for choosing this over x_ads_list_audiences or x_ads_dnr_users, so the guidance is implied rather than explicit.

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