list_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. It discloses that it lists files and folders, supports pagination (limit, offset), sorting (sort_by, sort_direction), and wildcard pattern filtering. It does not mention side effects (likely none) or permissions, but overall is transparent.

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 concise: a one-sentence introduction followed by a bullet-style parameter list. Every line adds value with no redundancy. It is well-structured and front-loaded.

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 an output schema present, the description does not need to explain return values. It covers all parameters and common constraints (e.g., pattern wildcards). Minor gaps: it does not specify that listing is non-recursive (only direct children) or clarify how offset works relative to limit. Still fairly complete.

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 adds critical meaning. It explains each parameter: path as full path, limit as max items, offset as pagination offset, sort_by with possible values (name, size, etc.), sort_direction as asc/desc, and pattern with wildcard support (e.g., *.pdf). This fully compensates for 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 description clearly states 'List files and folders at a given path,' specifying the action (list), resource (files and folders), and scope (path). This distinguishes it from siblings like search_files (content search) and get_file_info (single file details).

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 explains parameters but provides no explicit guidance on when to use this tool versus alternatives like search_files or get_file_info. Usage is implied through parameters (e.g., pattern for filtering), but no when-not or context is given.

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