download_result

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

Explicitly states 'No side effect', which is valuable since no annotations are provided. Discloses that the tool returns a URL (not the file), and explains the expected download process. Could mention error handling or rate limits, but overall good.

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 relatively concise with two clear parts: purpose and usage instructions. The inline command is lengthy but necessary for usability. Could be split into separate lines, but overall well-structured.

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?

For a simple tool with no output schema, the description covers the return type (URL) and downstream actions (curl/unzip). Missing details about error handling or URL validation, but these are not critical for a download URL getter.

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 already describes zip_url as 'URL of the result zip file (from get_task_status)'. The description adds context by stating the purpose is to return the zip URL from get_task_status, reinforcing the source and usage pattern.

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 action: 'Get the download URL for a completed parsing result'. It uses a specific verb and resource, distinguishing it from siblings like get_task_status which provides the URL source.

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?

Provides explicit post-call steps: download with curl and unzip. Implicitly ties usage to get_task_status by mentioning zip_url, but does not explicitly state when to use this vs alternatives.

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