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

The description's read-only claim ('List uploaded media') is consistent with the annotations readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so there is no contradiction. However, it adds little beyond the annotations: it does not mention pagination, authentication requirements, or what kind of media metadata is returned.

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 and front-loaded with the core action, but the 'Actions: list_images, list_videos' and '[Flattened action: list_images]' lines are redundant and potentially confusing for a specific tool. It is concise but not cleanly structured.

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?

Given no output schema and minimal parameter documentation, the description should provide more context about return values, filtering, or when to use the sibling upload/list tools. The current text covers only the basic operation and relies heavily on annotations and the tool name to fill gaps.

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 has 0% description coverage for the two parameters, and the description only hints at 'the ad account' as context. It does not explain the required format or role of 'account' or the meaning of 'auth_account', leaving both parameters largely underdocumented.

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 a read-only listing action ('List uploaded media in the ad account') and the flattened action 'list_images' pins the specific operation. It is mostly specific, though 'media' plus the mention of 'list_videos' slightly dilutes image-only clarity and could be confused with the sibling tool meta_ads_media_list_videos.

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 for when to use this tool versus alternatives. The description lists 'list_images, list_videos' and there is a sibling tool named meta_ads_media_list_videos, but it never explicitly says to choose this tool for images or explains exclusions such as video uploads.

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