meta_ads_creatives_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 explicitly states 'Read-only — does not modify the account' and discloses the default limit of 50 per call. This is valuable behavioral context beyond the schema, though it stops short of mentioning rate limits or API error behavior.

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, front-loaded with the primary action, followed by return fields, behavioral note, and usage guidance. It is efficient with no fluff or repetition of the tool name.

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 no output schema, the description lists the specific fields returned per creative (id, name, status, etc.). It also covers optional account_id fallback, pagination limits, read-only nature, and points to the sibling tool for ads, making this a complete and self-contained description.

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?

The schema fully documents both parameters (100% coverage), but the description adds practical guidance about using smaller limits and filtering client-side for large inventories. This insight goes beyond the schema's static default/max values, making the parameters more actionable.

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 AdCreative resources in a Meta Ads account' with a specific verb and resource, and enumerates the returned fields. It also distinguishes itself from the sibling tool meta_ads_ads_list by explicitly saying 'To list the ads that consume these creatives, use meta_ads_ads_list.'

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?

Provides explicit when-to-use guidance: 'Use this to audit creative inventory or to find a creative_id for reuse in meta_ads_ads_create.' It names the alternative for listing ads (meta_ads_ads_list) and offers practical advice about handling large inventories with smaller limits and client-side filtering.

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