yd_ad_images_add

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

No annotations provided, so description must carry the burden. It mentions the max limit but omits behavioral details like persistence, authentication needs, error behavior, or whether images become immediately available. The description is too sparse for full transparency.

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?

Two sentences, front-loaded with action and limit. Efficient but could include a note on return value or usage tip. No fluff.

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?

No output schema, so description should explain return behavior, but does not. It also lacks context on how uploaded images are referenced later, uniqueness of names, or error handling. Given the tool's data-creating nature, this is insufficient for full agent understanding.

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 coverage is 50% (client_login described, images parameter not described at top level). The description adds no parameter meaning beyond the schema—it does not explain name/image_data semantics, validation rules, or constraints like acceptable image formats.

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 tool's purpose: upload base64-encoded ad images. It includes a key constraint (max 100, recommended <=3) and distinguishes itself from sibling tools like yd_ad_images_delete and yd_ad_images_get.

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 on when to use this tool vs alternatives (e.g., yd_ads_add_image). No prerequisites, preconditions, or exclusions are mentioned, leaving the agent to infer usage context.

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