generate_download_script

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

With no annotations, the description carries full burden. It discloses that the tool optionally saves a script to file (making it executable with chmod 755) and includes MD5 verification commands. It also details the return dictionary. Missing are explicit mentions of overwrite behavior, permissions, or error handling, but overall it is sufficiently transparent for a script generation tool.

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 a clear header, Usage Tips, and Returns section. It is concise but comprehensive, front-loading the purpose. Slightly could be trimmed, but overall efficient.

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 schema coverage is 100% and an output schema exists (though not shown), the description covers purpose, usage workflow, and return values. It could mention idempotency or specific error conditions, but it is largely complete for a script generation 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 coverage is 100%, so baseline is 3. The description does not add new meaning beyond the schema's descriptions for each parameter; it focuses on usage and returns. No additional parameter semantics are provided.

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 opens with a specific verb+resource: 'Generate executable bash script to download all study data files.' This clearly distinguishes it from siblings like get_download_urls (URLs) and search_rna_studies (search).

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 Usage Tips section explicitly states 'After identifying interesting studies, generate a download script' and provides a typical workflow: search_rna_studies() → get_study_details() → generate_download_script(). This gives clear context for when to use it, though it does not explicitly list when not to use it or alternative tools.

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