List Ad Creatives

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is covered. The description adds a useful note about the return fields (creative IDs, names, and page post IDs), but does not disclose pagination behavior, API limits, or other operational traits beyond the 'after' cursor parameter.

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 compact and well-structured: one line states the purpose, a short Args block documents parameters, and a Returns line covers output. There is no redundant or wasted text.

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?

For a simple, read-only list operation, the description gives enough context to call the tool correctly: the required ad_account_id, pagination support, limit default, and the return shape. It does not discuss usage versus siblings, but the core invocation context is adequately covered.

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 only describes response_format, leaving ad_account_id, limit, and after undocumented. The description compensates by explaining each of these three parameters, including the default for limit and the purpose of after as a pagination cursor. It omits response_format, but that parameter already has a schema description.

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 action ('Lists ad creatives for an ad account') with a specific resource and scope. It is distinguishable from close siblings like meta_list_ads by the 'ad creatives' object, though it does not explicitly name or contrast any sibling tool.

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?

No guidance is provided about when to use this tool versus alternatives such as meta_list_ads, meta_list_campaigns, or meta_list_adsets. The context signals show a large sibling set, so explicit routing guidance would be valuable, but none is present.

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