meta_ads_creatives_list

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

The description explicitly states 'Read-only — does not modify the account', which is key behavioral info. It also explains the limit behavior (default 50, max 1000) and suggests filtering for larger inventories. However, it does not mention pagination mechanisms or rate limits, and with no annotations, these are minor gaps.

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 concise (four sentences) and front-loaded with purpose and return fields. Every sentence adds value: purpose, return fields, read-only status, limit behavior, and usage guidance with sibling links.

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?

The description covers the tool's purpose, return fields, read-only nature, limit details, and links to related tools. It does not mention error handling or permissions, but given no output schema, it adequately explains the list operation. Minor gap: no mention of prerequisites like account existence.

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?

Both parameters (account_id, limit) have full schema descriptions (100% coverage). The tool description adds practical advice about using smaller limits for large inventories, but this adds limited meaning beyond the schema's own descriptions. Baseline 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 AdCreative resources and specifies the exact fields returned (id, name, status, etc.). It distinguishes itself from sibling tools like meta_ads_creatives_create (create) and meta_ads_ads_list (list ads) by stating its read-only nature and linking to meta_ads_ads_create for creative_id reuse.

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 tells when to use this tool ('to audit creative inventory or to find a creative_id for reuse in meta_ads_ads_create') and provides a direct alternative ('To list the ads that consume these creatives, use meta_ads_ads_list'). This gives clear guidance on tool selection.

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