hunter_batch_task_result_download

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions saving locally and CSV format but does not cover error handling, file overwrite behavior, or network retry logic. Adequate for a simple download tool but lacks depth.

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 two sentences, each delivering essential information: the primary action and the necessary prerequisite. It is front-loaded with the core function, contains no redundant words, and every sentence earns its place.

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 that an output schema exists, the description need not explain return values. It covers the key aspects: action, format, save behavior, and usage context with sibling tools. Minor missing details like file size limits do not significantly detract from completeness.

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 the schema already documents all three parameters. The description adds value by confirming the download action and local save context, but does not provide additional constraints or meanings for parameters beyond what the schema states.

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 identifies the tool as downloading a CSV export file from Qianxin Hunter batch queries, and distinguishes it from sibling tools like hunter_batch_task_create and hunter_batch_task_progress by specifying the output format and local save behavior.

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 states the prerequisite of confirming task completion via hunter_batch_task_progress, providing clear when-to-use guidance. It does not, however, list alternative tools for when to not use this tool, but the context is implied.

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