syncthing_folder_defaults

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 by structured data. The description adds nothing beyond that — no note on whether defaults are instance-specific, how the optional instance parameter affects scope, or what the OpenWorld behavior means here. It does not contradict the annotations, but it contributes zero behavioral context.

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 words is short, but this is under-specification rather than conciseness — there is no front-loaded statement of action or result to be concise about. The single fragment carries no information beyond the tool name.

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?

With no output schema and no description of return values, an agent has no idea what this read operation yields (a config object? a list of field names? defaults for which instance?). For a two-parameter tool with zero parameter documentation, the definition is completely inadequate.

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?

Both parameters ('fields' and 'instance') have 0% schema description coverage and receive no explanation in the description. The optional 'fields' array (max 30 items) and the 'instance' selector are left entirely unexplained, so the description fails to compensate for the documentation 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 defaults." is a noun phrase that essentially restates the tool name (syncthing_folder_defaults) without stating a verb or what is actually returned. An agent cannot tell from this whether it fetches default folder configuration, resets folders to defaults, or lists default settings — and it is not distinguished from siblings like syncthing_folder_config or syncthing_ignore_defaults.

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?

There is no when-to-use guidance, no mention of alternatives such as syncthing_folder_config, and no stated preconditions. The description offers no signal about when this tool should be preferred over the many other folder-related siblings.

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