List folder

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

Beyond readOnlyHint and openWorldHint, the description discloses pagination/truncation behavior and recursion semantics. It does not cover output item shape or ordering, but the annotations already cover safety and the added behavioral traits are useful.

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?

Three short sentences, front-loaded with the action, with no filler. Every sentence contributes actionable guidance.

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?

Covers core invocation, root handling, recursion, and pagination. Missing return item shape and limit semantics, but given the annotations and the simplicity of a list operation this is largely sufficient.

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 description explains the non-obvious semantics of path (root), recursive (walk subfolders), and cursor (continuation after truncation). limit is not explained in prose, but its name and min/max constraints make its purpose reasonably inferable.

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?

States a specific verb ('List') and resource ('contents of a folder'), and clarifies root and recursion. This clearly distinguishes it from siblings such as dropbox_get_metadata or dropbox_read_file.

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?

Provides explicit how-to guidance: root path, recursive=true, and cursor for truncated results. It does not explicitly name alternatives or when not to use it, but the context is clear enough for an agent to select it for folder listing.

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