kadam_adv_upload_bulk_images

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

Annotations only tell the agent readOnlyHint=false; the description adds substantial behavioral context beyond that: asynchronous queuing that returns a job rather than staged IDs, format validation against target campaigns, quota consumption against the daily creative limit, and batch rejection on overage. These are exactly the non-obvious traits an agent needs.

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?

Four tight sentences, front-loaded with the core purpose, then constraints and async behavior. Every sentence carries information; none is redundant.

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 exists, but the description explains the return (a job, not immediate staged IDs), how to retrieve results, and the quota/rejection behavior. Combined with 100% schema coverage, nothing an agent needs to invoke it correctly is missing.

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 100%, so the baseline is 3. The description still adds meaning beyond the schema by noting that images are format-checked and that campaignIds must reference mutually compatible campaigns, which is not expressible in the schema. idempotencyKey and image format are already covered by the schema.

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?

States a specific verb and resource ('stage images so they can be turned into creatives') and positions itself as 'first step of a bulk creative batch'. It names the follow-up sibling kadam_adv_get_bulk_job, so an agent can distinguish this staging step from the creation step without reading either schema.

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?

Clearly sets context as the first step of a bulk batch and explicitly routes to kadam_adv_get_bulk_job for retrieving results. It does not, however, state when-not to use it (e.g. vs create_creative for single creatives) or exclusions, so it falls short of a full when/when-not treatment.

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