⚠️ Autoload: launch upload

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

Annotations indicate destructive (destructiveHint=true) and not idempotent. Description adds critical context: side effect of publishing/updating listings, publication limits do NOT apply, and the one-per-hour rate limit. No contradiction with 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?

Single paragraph densely packs purpose, side effects, limits, and parameter explanations. Slightly dense but each sentence is justified. Could be broken into shorter sentences for readability.

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, but description adequately explains return ('launch confirmation') and directs to polling via a sibling tool. Covers all necessary aspects for a 2-param tool: behavior, params, limits, and follow-up.

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%, baseline 3. Description adds meaning: dryRun as safe preview, idempotencyKey with conflict handling and key storage details. This improves understanding beyond schema 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 immediately launches an unscheduled upload of listings from the feed URL set via autoload_create_or_update_profile_v2. It distinguishes from sibling tools by mentioning the dryRun and idempotencyKey, and directs polling via autoload_get_last_completed_report_v3.

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?

Explicit guidelines: use to trigger immediate upload, notes that all listings are processed without limit from settings, mentions one upload per hour, and explains when to use dryRun (preview) and idempotencyKey (duplicate protection). Indirectly tells when not to use (if you want scheduled uploads or to avoid all listings).

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