meta_ads_ads_list

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

With no annotations, the description carries full burden. It declares 'Read-only', lists returned fields, and explains limit behavior (Meta Graph API caps at 1000 per page) with suggestion for larger sets. Does not mention auth requirements explicitly, but the read-only nature and parameter descriptions are sufficiently transparent.

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 focused sentences with no fluff. First sentence covers purpose and output, second declares read-only, third gives usage guidance, fourth links to related tool. Every sentence earns its place.

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?

No output schema exists, but the description lists all returned fields. Parameters are fully described. The tool is simple and the description covers scoping, read-only behavior, and limitations (limit cap). Adequate for an agent to use correctly.

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 100%, so baseline is 3. The description adds meaning: account_id format and fallback, ad_set_id restricts scope, limit includes max and guidance for larger results. This goes beyond the schema descriptions.

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 'Lists ads' with specific scoping to account and optionally ad set. It distinguishes from sibling tools like meta_ads_ads_get (single ad) and meta_ads_ads_create by indicating it returns a list and is read-only. Also lists specific fields returned, reinforcing its purpose.

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?

Explicitly states when to use: 'Use this to find an ad_id before calling ads.update / pause / enable, or to audit which creatives are in flight.' Also provides an alternative: 'For the creative itself... follow up with meta_ads_creatives_list.' This gives clear context and exclusions.

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