list_list_targets

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

With no annotations provided, the description carries full behavioral transparency burden, but it only restates the listing action. It does not disclose that this is a read-only operation, how pagination behaves beyond the schema defaults, or any side effects. The absence of safety or behavior notes is a notable gap.

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, front-loaded sentence with zero unnecessary words. It states the action and clarifies the domain in a parenthetical, making it concise and well-structured.

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?

For a simple list operation with two optional pagination parameters, the description is minimally adequate, but it leaves gaps: no output schema means the agent doesn't know the return structure, and there's no mention of whether 'all' means across all scopes (e.g., advertiser, account) or any filtering/ordering behavior.

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%, with clear descriptions for limit (default 100, max 100) and offset (pagination offset). The tool description itself adds no parameter-specific semantics, so the baseline of 3 applies as the schema already documents the parameters.

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 'List' and the resource 'list targets', with a clarifying parenthetical '(allowlist/blocklist targeting)'. This distinguishes it from sibling tools like get_list_target, create_list_target, and other target-type listers (e.g., list_data_key_targets, list_platform_targets).

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 usage is implied by the name and description: use this to list list targets, presumably when you need the full set rather than a single target (which would use get_list_target). However, there is no explicit when-to-use vs alternatives, no exclusions, and no mention of prerequisites or scope.

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