meta_ads_pages_photos_list

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

With no annotations provided, the description carries the full burden and meets it well: it declares the operation read-only, lists the returned fields, states default and maximum limits, and discloses that Meta's support for reusing Page photos as covers is undocumented. It even gives a fallback strategy rather than suggesting retries.

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 dense but every sentence earns its place: purpose, return shape, read-only status, integration path, caveat, limits, and prerequisite. It is front-loaded with the core purpose and then layers the critical integration warnings.

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?

Although there is no output schema and no annotations, the description covers return values, behavioral safety, defaults, caveats, and the correct call sequence relative to sibling tools. An agent has enough context to invoke the tool correctly and know what to do with the results.

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%, so the schema already documents each parameter thoroughly. The description adds some context, such as the limit rationale and that the page should be the same one the lead form belongs to, but it does not need to compensate for missing schema coverage. 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 opens with a specific verb and resource: 'Lists photos a Facebook Page has already uploaded,' and immediately ties it to a concrete purpose: reusing one as an Instant Form cover. It also differentiates this tool from the sibling meta_ads_images_upload_file by noting that this returns PAGE photo ids, not ad-account image hashes.

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?

Usage guidance is explicit and actionable: use the returned `id` as `context_card.cover_photo_id` for meta_ads_lead_forms_create, avoid the `image_hash` from meta_ads_images_upload_file, and use meta_ads_pages_list first when page_id is unknown. It also tells the agent what to do if the create call rejects the id.

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