List Ad Images

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the resource scope ('image library') and notes the default limit, but does not disclose pagination behavior, return shape, or the meaning of the 'after' cursor. With annotations handling the primary behavioral traits, this is adequate but not rich.

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 short, front-loaded, and free of fluff. The Args block is easy to scan. It loses one point only because the missing 'after' parameter means it is concise but not as useful as it could be.

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 list operation with no output schema, the description should explain enough for correct invocation. It gives the required ad_account_id and the limit default, but fails to describe the 'after' pagination parameter, the response_format option, or what the returned image data contains. This is a notable completeness gap for a paginated list endpoint.

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 only 25%, so the description must compensate. It explains ad_account_id and limit, but omits 'after' entirely, which is likely a pagination cursor and is also undocumented in the schema. This is a meaningful gap because a listing tool without pagination guidance is incomplete for the agent.

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 states a specific verb and resource: 'Lists images in an ad account's image library.' This clearly distinguishes it from sibling tools like meta_upload_ad_image, meta_list_ad_videos, and meta_list_ad_creatives by narrowing the resource to images in the ad account library.

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 implies when to use the tool: whenever you need to list ad account images. However, it does not explicitly state when not to use it, nor does it mention alternatives such as meta_list_ad_videos or meta_upload_ad_image, leaving selection to inference.

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