onelake_ls

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

With no annotations, the description must carry the full behavioral disclosure burden, but it only states the listing action. It does not mention recursion behavior, path defaulting, workspace or lakehouse requirements, permissions, or return format, leaving the agent to guess.

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, front-loaded sentence with no filler or repetition. It is appropriately concise for a straightforward list operation, even though other dimensions penalize the lack of supporting detail.

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?

For a tool with no annotations, no output schema, and three undocumented parameters, this description is not sufficient. An agent knows the tool lists files and folders but cannot reliably determine how to supply workspace/lakehouse/path or what the result structure looks like, especially given the large sibling toolset.

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 must compensate, but it only clarifies that 'path' refers to a OneLake lakehouse path. It gives no meaning for the 'lakehouse' or 'workspace' parameters and no detail about default values or how the path is resolved.

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 uses the specific verb 'List' and resource 'files and folders within a OneLake lakehouse path,' which makes the core operation clear. It does not explicitly differentiate from sibling tools like onelake_list_shortcuts or list_lakehouses, so it stops short of full sibling differentiation.

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 such as onelake_read, onelake_list_shortcuts, or list_lakehouses. The description only states the action and gives no contextual triggers, exclusions, or preferred usage patterns.

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