List Nextcloud files

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, deterministic read operation. The description adds meaningful behavioral context beyond the annotations: it limits results to direct children and constrains paths to within the configured root.

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, focused sentence with no filler or redundant information. It conveys the core action, scope, and location in a compact way.

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 simple list operation with one optional parameter, read-only annotations, and an output schema, the description covers the essential behavioral context: non-recursive listing within a root-relative folder. It does not mention pagination or hidden files, but the output schema likely covers return structure, and the tool is simple enough that this is not a major gap.

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% for the single 'path' parameter, so the description must compensate. It implies the path refers to a folder and is root-relative, but it does not clarify the default behavior of an empty path, whether leading slashes are accepted, or that the path must identify a folder rather than a file.

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 a specific verb and resource: 'List direct children of a folder inside the configured Nextcloud root.' It distinguishes itself from siblings like search_files and get_file_info by emphasizing 'direct children' and the root-relative scope.

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?

The phrase 'direct children' provides clear context that this is non-recursive, and 'inside the configured Nextcloud root' sets a scope boundary. It does not explicitly name alternatives or when-not-to-use cases, but the context is strong enough for an agent to differentiate from recursive search or file-reading tools.

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