dbfs_list

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

The description aligns with the annotations (readOnlyHint=true) by stating a read operation. However, it does not disclose additional behavioral details such as pagination, error handling when a path does not exist, or whether the listing is recursive. Given the annotation already covers the safety profile, the description adds minimal extra transparency.

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 very concise at one sentence (7 words) and front-loads the verb and resource. It contains no unnecessary words. However, its brevity may omit useful context like output format (though covered by output schema). It earns its place but could be slightly more informative.

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 tool's low complexity (one parameter, simple list operation) and the presence of annotations and output schema, the description is complete enough. It states what the tool does and implies the input (directory path). The output schema likely documents the return structure, so the description does not need to repeat it. A minor gap is the lack of mention of non-existent paths, but overall acceptable.

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 input schema already fully describes the 'path' parameter (100% coverage) with a clear description ('Absolute DBFS path to list'). The description only restates the general action and does not add any semantic value beyond the schema, such as format constraints or examples. Thus, it meets the baseline for fully covered parameters.

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) and resource (contents of a DBFS directory), distinguishing it from siblings like dbfs_get (which retrieves file content) and dbfs_get_status (which gets metadata). The verb 'list' and resource 'contents of a DBFS directory' directly convey the tool's purpose.

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?

There is no guidance on when to use this tool versus alternatives. Among siblings like dbfs_get, dbfs_get_status, or dbfs_delete, the description does not provide context or exclusions, leaving an agent to infer usage without explicit when-to or when-not-to information.

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