List lead gen forms

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: no word on pagination aggregation (max_pages merging), result ordering, or what an empty account returns — all of which matter for a network-backed list call.

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 short sentence with the scope front-loaded and zero filler. It is efficient rather than padded; the only weakness is that it is thin rather than that it is verbose, which is better assessed under completeness.

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 a fully documented schema and read-only annotations, an agent has enough to call this correctly. What is missing is whether listing supports filtering (e.g. by campaign or status) and how pagination behaves at the tool level, which the description could have clarified for a zero-required-parameter list operation.

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% — every parameter (ad_account_id, page_token, page_size, max_pages) carries its own documentation, including the default account fallback and pagination merge semantics. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ('List') and resource ('lead generation forms') scoped to an ad account, so an agent can tell what it returns. It does not distinguish itself from the sibling reddit_ads_get_lead_gen_form (single form) or reddit_ads_create_lead_gen_form, leaving the singular-vs-plural routing to inference.

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 statement of when to use this tool, when not to, or which sibling to prefer for a single form vs a full listing. List semantics make the basic usage self-evident, but that is inference on the agent's part rather than guidance in the definition.

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