list_ads

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

With no annotations provided, the description carries the full behavioral burden. It conveys that this is a read-only listing operation scoped to the ad account and that results can be narrowed by campaign_id or ad_group_id. However, it does not disclose pagination semantics (after/before/limit), ordering behavior, or output structure, despite these being present in the schema.

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?

Two sentences with no filler; the core function and filtering behavior are front-loaded. The second sentence adds a valuable routing note that helps prevent misuse of list_ads for single-ad retrieval.

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?

Without an output schema or annotations, the description should provide more operational context, but it omits pagination, ordering, include behavior, and the role of ad_account_id. The nine-parameter schema and large sibling-tool set suggest richer guidance is needed for correct invocation.

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?

Only campaign_id and ad_group_id receive semantic clarity via 'optionally filtered,' while the other seven parameters—name, after, limit, order, before, include, and ad_account_id—are left unexplained. With schema description coverage at only 22%, the description should compensate but covers only two of nine 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 uses a precise verb–resource pair ('List ads') and scopes it to 'the ad account.' It also names the two optional filter fields and points to get_ad / insights / preview for ad_id, which clearly distinguishes this list operation from single-ad sibling tools.

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 sentence 'Use ad_id for get_ad / insights / preview' gives an explicit routing rule for when an ad_id is already known. It implies list_ads is for enumeration and filtering, but it does not explicitly name alternatives like list_campaigns or list_ad_groups, nor does it state when not to use the tool.

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