upload_ad_image

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the optional access token and default name behavior, but lacks critical details: required permissions, rate limits, file size/format constraints, error handling, or whether the operation is idempotent. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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 well-structured with clear sections (purpose, args, returns) and front-loaded core functionality. Every sentence adds value, though the parameter explanations could be slightly more concise. No redundant or wasted content.

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 5 parameters, no annotations, but an output schema exists, the description is moderately complete. It covers parameter semantics well and mentions the return format, but lacks behavioral context (permissions, limits) and doesn't fully compensate for the missing annotations. The output schema reduces need for return value details, but other gaps remain.

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 0%, so the description must compensate. It provides meaningful context for all 5 parameters: clarifies account_id format, explains access_token fallback behavior, specifies file/data URL formats, distinguishes image_url as a fetch source, and notes name's default behavior. This adds substantial value beyond the bare schema, though some details like exact base64 requirements remain unspecified.

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 specific action ('Upload an image') and resource ('to use in Meta Ads creatives'), distinguishing it from sibling tools like 'get_ad_image' (which retrieves) or 'create_ad_creative' (which uses uploaded images). The verb+resource combination is precise and unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active ad account), compare with similar tools like 'get_ad_image', or specify scenarios where direct upload is preferred over other methods. Usage context is implied but not explicit.

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