List Nextcloud files

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile and the 'no public web' constraint are partly redundant with structured data. The description does add real context — the listing is non-recursive and scoped to the authenticated user's own workspace root — but says nothing about ordering, pagination/limits, hidden files, or how large directories are handled.

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?

Two tight sentences with zero filler; the core action and scope lead, and the constraint sentence follows. Nothing is repeated from the title or annotations verbatim.

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 single-optional-parameter read tool with an output schema (so return shape need not be described) and annotations covering safety and openness, the description supplies what remains: non-recursive listing and root-relative path scoping. Details like ordering and page limits are the only omissions and are minor at this complexity.

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 coverage is 0% and the single 'path' parameter has no description, default-to-root explanation, or format guidance in the schema. The description partially compensates by stating paths are relative to the workspace root, but it never says what an empty/omitted path resolves to or whether a folder path requires a trailing slash.

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 and resource — list direct children of the connected private Nextcloud workspace root — and pins the scope with 'direct children' (implying non-recursive) plus the explicit exclusion of other accounts, hosts, and the public web. It never names the sibling it is most easily confused with (search_files), so sibling differentiation is left implicit rather than stated.

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 by the scope statement: it is the tool for enumerating one directory of the private workspace. The 'cannot browse another account, host, or the public web' sentence functions as a when-not, but no alternative tool is named and there is no guidance on when to prefer search_files or get_file_info instead.

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