list_folder

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

Although 'list' implies read-only, no explicit behavioral traits are disclosed beyond the basic operation. No annotations exist to compensate, so the description should detail side effects, recursion, or hidden file handling.

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 front-loaded with the core purpose and follows a clear Args format with no redundant information.

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 an output schema exists, the description needn't detail return values. It covers parameters and purpose adequately, but could mention recursion or hidden file behavior.

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 description adds full parameter semantics (folder_path as absolute path, pattern with examples and default), which the schema lacks entirely (0% coverage). This compensates well.

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 'List files in a folder' with a specific verb and resource, distinguishing it from siblings like read_file and scan_folder_for_intent.

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 provides parameter details but no guidance on when to use this tool versus alternatives such as scan_folder_for_intent or search_fulltext.

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