Download ENCODE Files

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

The description discloses MD5 verification, concurrent downloads, and skip-if-already-downloaded behavior. Annotations indicate readOnlyHint false, destructiveHint false, idempotentHint true, openWorldHint true, with no contradictions. The description adds valuable context beyond annotations.

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 brief summary, detailed features, usage guidance, and a parameter list. It is concise, with no extraneous information, and each sentence adds value.

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 4 parameters, 0% schema coverage, output schema presence, and annotations, the description provides complete guidance: parameter details, return format, and behavioral traits. Nothing essential is missing.

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?

Despite 0% schema description coverage, the description includes a detailed 'Args' section explaining each parameter with examples, defaults, and enum options for 'organize_by'. This fully compensates for the missing schema descriptions.

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 name and title clearly indicate downloading ENCODE files. The description specifies 'Download specific ENCODE files by accession to a local directory,' using a specific verb and resource, and distinguishes from sibling tools like encode_batch_download.

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 'WHEN TO USE: Use for downloading specific files by accession. For bulk downloads, prefer encode_batch_download.' It also lists related tools, providing clear guidance on when to use this tool versus alternatives.

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