list_data_files

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

Although annotations already declare readOnlyHint=true, the description adds substantial behavioral context: default extension filtering, the full raw-data extension list, the fact that some raw formats are folders indicated with a trailing slash, and that absolute paths are returned for direct downstream use.

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 opening sentence states the purpose immediately, then structured bullets cover each parameter without redundancy. The raw extension lists are long but necessary for correct usage, and the final sentences give useful downstream context without waste.

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 read-only listing tool with three optional parameters and no output schema, the description is complete: it explains defaults, filtering, raw-file inclusion, folder-based formats, return format, and likely next steps. An agent has everything needed to select and invoke it correctly.

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%, so the description must carry parameter semantics, and it does: directory has a defined default via LIPIDMIX_DATA_DIR or <project>/data, extension is explained with examples, and all_files is explained with its default filtering behavior and the exact raw extensions it unlocks.

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 uses a specific verb-resource pair: it lists analysis target files in the data folder by extension. It clearly distinguishes the default analyzable-file behavior from raw measurement data and points to sibling tools like pai2_parser and load_dataset for next steps.

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?

It explicitly says when to use all_files=True versus the default, provides examples for extension filtering, and directs agents to load_dataset when the intent is to analyze an entire folder. This gives clear when-to-use and alternative guidance.

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