meta_ads_ads_list

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

No annotations are provided, so the description carries the full burden. It states 'Read-only,' which is a key behavioral trait. The limit parameter description hints at pagination behavior (max 1000 per page, default 50). It does not detail error cases or rate limits, but for a read-only list tool, this is sufficient.

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 four sentences: first states purpose, second lists return fields, third declares read-only and usage, fourth gives follow-up. Every sentence adds value, and the structure is front-loaded with key information.

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?

Given no output schema, the description explains the exact fields returned. It also provides context on how to use the tool in conjunction with sibling tools for mutation and creative inspection. For a list tool, this is complete and actionable.

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% (all three parameters have descriptions in the schema). The description adds contextual usage flow but does not substantially expand on parameter meanings beyond the schema, which already explains them well. The baseline of 3 is appropriate.

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 tool lists ads in a Meta Ads account, optionally scoped to an ad set, and specifies the returned fields. It distinguishes itself from sibling tools like meta_ads_ads_update by explicitly noting its use to find an ad_id before calling update/pause/enable, and mentions meta_ads_creatives_list for creative details.

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 description explicitly directs when to use this tool ('Use this to find an ad_id before calling ads.update / pause / enable, or to audit which creatives are in flight') and provides a follow-up action for creative details, offering clear context about alternatives.

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