start_download_result

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

No annotations are provided, so the description carries full burden. It discloses that the tool starts a background download (non-blocking), returns a task_id, and specifies the source of task_uuid. It could be more explicit about error handling or idempotency, but the main behavioral traits are covered.

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 numbered steps and explicit Args/Returns sections. It is concise with no superfluous information, every sentence serves a purpose.

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 the tool's simplicity and the presence of an output schema, the description covers all necessary aspects: purpose, parameters, usage context, and follow-up actions. It is complete for an agent to correctly invoke the 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 description coverage is 0%, so the description must compensate. It explains task_uuid as the UUID from generate_3d_* (not subscription_key) and output_dir as the folder for files with a default. This adds significant meaning beyond the schema's null titles.

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 starts a background download of 3D task results, specifying the verb ('запускает фоновую загрузку') and resource ('результаты 3D-задачи'). It distinguishes from sibling tools like check_download_result_status and generate_3d_* by indicating it is used after generation completion.

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?

Explicitly states when to use: after generation is completed (check_task_status). It clarifies the tool is non-blocking and that the returned task_id should be passed to check_download_result_status. This provides clear sequential guidance.

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