Get Meta Ad Image by Hash

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

Annotations already indicate readOnly and idempotent; description adds value by detailing returned fields (CDN url, dimensions, name, status) and contextualizing hash origin. No contradiction.

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?

Short, front-loaded with main action, every sentence informative. No wasted words.

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?

Covers purpose, usage, and key return values. Lacks error handling or edge cases, but sufficient for a simple lookup tool given annotations and schema.

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 50% (only act_id described). Description adds context for image_hash (where it comes from) but not for act_id. Partially compensates for missing 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?

Description clearly states 'Look up a single image... by hash,' specifying verb, resource, and key parameter. It distinguishes from siblings by focusing on single hash-based retrieval, contrasting with batch or other retrieval tools.

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?

Description provides explicit use case when you have a hash and need the URL, referencing related functions like upload_ad_image. However, it doesn't explicitly state when not to use or mention alternatives like meta_ads_get_ad_images for multiple hashes.

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