⚠️ Autoload: launch upload

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

Annotations already indicate destructive and non-read-only behavior. The description adds that publication limits do not apply and that all listings are processed. It also warns about the side effect (publishing/updating/activating listings) and describes dryRun as a safe preview. This adds value beyond annotations.

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 dense but well-organized, front-loading the action and side effect. It could be broken into bullet points for clarity, but it remains concise and informative with 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?

Despite no output schema, the description explains return value (launch confirmation) and directs polling. It covers all critical aspects: trigger, side effects, limits, parameters, and alternative actions (dryRun preview). Complete for a launch tool.

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 parameters are documented. The description adds meaning: dryRun previews without calling Avito, idempotencyKey provides duplicate protection. This goes beyond the schema's basic descriptions.

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 launches an unscheduled upload of listings from a feed URL specified in the profile. It uses a strong verb ('LAUNCHES') and specifies the resource (upload from profile settings). It distinguishes from sibling tools like autoload_create_or_update_profile_v2 which sets up the profile.

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 clear context: it's for immediate uploads, has a one-per-hour limit, and suggests polling for results via autoload_get_last_completed_report_v3. It does not explicitly mention when not to use it, but the context is sufficient.

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