syncthing_folder_browse

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

Annotations declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing on top: it does not say whether browsing hits the local or a remote instance, whether the folder must exist/be configured, how recursion via levels behaves, or how pagination via cursor/limit is surfaced.

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?

It is short, but brevity here reflects under-specification rather than economy: two words that carry no actionable content and are not front-loading anything useful.

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 read tool with seven parameters, pagination, recursion depth, and field selection, plus no output schema to explain returns, two words are wholly inadequate. An agent cannot determine what will be browsed or what comes back.

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?

Seven parameters (folder, prefix, levels, limit, cursor, fields, instance) with 0% schema description coverage, and the description explains none of them. Terms like levels (recursion depth) and prefix (path scoping) are non-obvious and go completely undefined, so the description fails to compensate for the schema gap.

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?

"Folder browse." is essentially a restatement of the tool name (syncthing_folder_browse) with no distinguishing detail. It does not explain what browsing returns (directory listing? sync state? file tree?) or how it differs from siblings like syncthing_folder_status, syncthing_folder_completion, or syncthing_local_changes.

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 when-to-use, prerequisites, or alternatives are given. It is not misleading, just silent, so this is pure absence of guidance rather than an error.

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