workspace_list_files

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

The description adds minor behavioral context by specifying the path prefix, but it does not describe the output format, pagination, or any side effects. The readOnlyHint annotation is already present, so the description does not significantly enhance transparency beyond acknowledging the read-only nature.

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 a single sentence that conveys the core functionality without extraneous words. It is appropriately sized for a simple list operation, though it could be slightly expanded for clarity.

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 the simplicity of the tool (one parameter, read-only, output schema present), the description covers the essential purpose. It does not detail return attributes, but the output schema likely handles that. The description is adequate but not comprehensive.

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 100%, and the tool description merely repeats the parameter's purpose already stated in the schema. It adds no additional semantics or contextual details.

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 the action ('List files') and the specific resource path ('/Workspace/files/<directory_path>'). It distinguishes from sibling tools like workspace_list and dbfs_list by narrowing the scope to a particular directory prefix.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., workspace_export, workspace_read_file). The annotation readOnlyHint is not mentioned, and there is no discussion of prerequisites or context.

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