list_ads

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds useful context that results include approval status, but it does not describe pagination, filtering behavior beyond the parameter, or other response characteristics. This is adequate given the annotation coverage.

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 two focused parts: a one-sentence purpose and a compact Args block. Every line earns its place, and the main purpose is front-loaded before parameter details.

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 read-only list operation with annotations covering safety and open-world semantics, the description supplies enough information to invoke the tool correctly: purpose, required ids, optional filter, and limit. No output schema exists, but the phrase 'with approval status' gives the main expected return context.

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%, and the description fully compensates by explaining every parameter: customer_id, ad_group_id, status_filter with allowed example values, and limit with default and meaning. It adds value well beyond the bare schema.

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 states a specific operation: 'List ads in an ad group with approval status.' This clearly distinguishes it from siblings like list_ad_groups (lists groups) and get_ad_details (single ad detail), and the resource and plural scope are unambiguous.

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?

It clearly implies the tool is for retrieving ads within a specific ad group, and it defines the optional status_filter. It does not explicitly name alternatives or exclusion criteria, but the context is sufficiently clear for selecting it over the read/ad-group siblings.

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