download_result

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

No annotations exist, so the description must cover behavioral traits. It does so by stating 'This tool is blocking: LLM waits for the download to complete within a single call.' This is key behavior beyond the obvious. Also mentions the return format.

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: first sentence states purpose, then blocking nature, then comparison with alternatives, then parameter descriptions, then return value. All sentences are relevant, though slightly verbose. Front-loaded with key information.

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 (2 parameters, download operation), the description covers all necessary aspects: purpose, blocking behavior, alternative usage, parameter details, and return format. It is complete for effective use.

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 adds essential meaning. It clarifies that task_uuid is 'the uuid field from generate_3d_*, not subscription_key' and describes output_dir as 'Folder to save files; default is current directory.' This is highly informative.

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: 'Synchronously downloads the results of 3D model generation by task UUID.' It also distinguishes itself from the sibling tool pair start_download_result + check_download_result_status.

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 explicitly provides guidance on when to use this tool versus the alternative: 'Usually it is preferable to use the pair start_download_result + check_download_result_status, but download_result is convenient for simple scenarios and small data volumes.'

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