Download NEON files

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

The annotations already mark this as idempotent and non-destructive, but the description adds useful details: writes into a download directory, requires a token for data files, checks size limits, verifies MD5s, and skips identical existing files. It goes meaningfully beyond the structured annotations, though it does not cover error or failure behavior.

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 short and front-loaded, with each sentence serving a distinct purpose: scope, safety behavior, and next steps. The parentheticals add density, but the description remains efficient and readable.

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 20-parameter tool with no required parameters, the description gives useful context and the schema carries the individual parameter details. However, it does not explain which parameter groups are required for each download mode, how to discover file names via sibling tools, or the setup needed for the token, leaving some completeness gaps.

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?

The input schema has 100% parameter coverage, but the description adds useful semantic structure by grouping parameters into download modes: data files/package ZIPs, prototype datasets, and NEON documents. It also surfaces behaviors tied to parameters like byte caps and skip-if-identical, which helps an agent form a valid parameter combination.

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 downloads NEON data files, package ZIPs, prototype dataset files, or NEON documents into a configured download directory. It does not explicitly distinguish itself from overlapping siblings such as neon_get_document or neon_list_files.

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 gives a workflow hint ('read the CSVs ... cite with neon_get_citation') and notes that data files need a token, but it does not say when to prefer this tool over its siblings or what to do before calling it. No exclusions, prerequisites beyond the token, or alternative-tool routing are provided.

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