files_list

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

Describes depth parameter behavior (0 for item itself, 1 for children) but lacks disclosure of error responses, authentication requirements, or read-only nature. No annotations to supplement.

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?

Two sentences plus parameter descriptions. Well-structured and front-loaded. Minor improvement could combine parameter info more concisely.

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?

Output schema exists, so return values are covered. Missing context on authorization, rate limits, or behavior for invalid paths. Adequate for a simple list 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 coverage is 0%, but description fully explains both parameters: path default '/', depth values '0' and '1'. Adds meaning missing from the raw 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?

Clearly states 'List files and folders at a WebDAV path' with specific verb and resource. Distinguishes from siblings like files_get (single file) and files_delete.

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?

Implies usage for listing directory contents but provides no explicit guidance on when to use this tool vs alternatives like files_get or files_search (nonexistent). No exclusions or context provided.

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