list_files

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

No annotations are provided, so the description carries the full burden. It makes the read-only nature evident through 'List' and explains pagination with offset and limit. However, it does not disclose potential errors, permission requirements, or whether the listing is direct-children-only or recursive.

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 tightly structured docstring with a front-loaded purpose sentence followed by a clear parameter list. Every line earns its place, and it avoids fluff while covering all key details.

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 output schema exists and the tool is a straightforward directory listing, the description covers the essential context: path, pagination, and sorting. A small gap is the lack of explicit mention that only direct children are listed, but the phrasing 'at the given path' implies this.

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?

With schema description coverage at 0%, the description thoroughly compensates by explaining every parameter: path with examples, limit range (1–100), offset for pagination, and sort field values including descending prefix '-'. This adds meaning far beyond the bare 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?

The description opens with a clear verb and resource: 'List files and folders at the given Yandex Disk path.' It specifies path-based listing, which is distinct from siblings like list_recent_files or list_trash, though it does not explicitly name those alternatives.

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?

Usage is implied through the path parameter and listing semantics, but the description provides no explicit 'when to use this vs. search_files or list_recent_files' guidance. It does not state exclusions or mention when a different tool would be more appropriate.

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