list_dataset_files

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It hints that the output includes file paths usable with open_session, but it does not state that the operation is read-only, how limit or version affect results, or what the response contains beyond vague file categories.

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 avoids verbosity, but it is awkwardly structured: the first sentence is a fragment and the second sentence discusses open_session rather than this tool's own invocation. It is economical but not optimally front-loaded or focused.

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?

With three parameters, no annotations, and no output schema, the description needed to provide substantial context, but it only gives a loose file-category summary and one cross-tool pointer. Parameter semantics, return shape, and practical invocation details are missing, so an agent cannot confidently call the 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 description coverage is 0% and the description never explains dandiset_id, limit, or version. An agent cannot infer the expected ID format, defaulting behavior, or how version controls the listing. The description does nothing to compensate for the undocumented schema.

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 names the resource (DANDI dataset) and the specific file categories (licence, citation, NWB files), which gives a clear sense of what the tool returns and distinguishes it from siblings like list_sources or search_datasets. It lacks a main verb and relies on the tool name for the 'list' action, so it is clear but not fully explicit.

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?

There is no statement of when to choose this tool over the list_sources, search_datasets, or open_session alternatives. The second sentence only tells the caller to pass a file path to open_session afterward, which is downstream guidance rather than selection criteria.

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