syncthing_gui_config

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

The description adds nothing beyond what annotations already state. With readOnlyHint=true it is a safe read, but the description gives no indication of what configuration is read, its scope, or the instance selection behavior, leaving the behavioral burden entirely on the structured metadata.

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 that convey no actionable information. This is under-specification, not conciseness; there is no structure or front-loaded content to evaluate.

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?

A 2-parameter config-access tool with no output schema and no annotations explaining behavior needs a description that at least names the resource and its parameters. This one supplies none of that.

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 two parameters (fields, instance). The description must compensate and does not — "fields" (a list of up to 30 strings) and "instance" (a string identifier) are completely unexplained.

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?

"Gui config." merely restates the tool name (syncthing_gui_config) without a verb or any indication of whether it reads, writes, or otherwise manipulates GUI configuration. It cannot be distinguished from siblings such as syncthing_config, syncthing_ldap_config, or syncthing_folder_config.

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 guidance on when to use this tool versus the many sibling *_config tools. No context, prerequisites, or alternatives are mentioned.

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