syncthing_folder_config

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. However, the description adds zero behavioral context beyond that – it doesn't say what configuration data is returned, whether instances are required, or any other operational trait. No contradiction with annotations.

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 are far too terse to be useful; this is under-specification rather than conciseness. The description fails to front-load any useful information because there is none to front-load.

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 tool that likely retrieves folder configuration with three parameters and no output schema, the description is completely inadequate. It leaves the agent unable to invoke the tool correctly or understand its role among 39 sibling tools.

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% across three parameters (folder, fields, instance), and the description says nothing about any parameter. With low schema coverage, the description must compensate, but it provides no semantic detail whatsoever.

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?

Description is 'Folder config.' – a noun phrase that restates the tool name without a verb, scope, or any distinguishing detail. It reads as a label rather than a purpose statement, leaving the agent unable to tell what the tool does or how it differs from sibling tools like syncthing_folder_defaults or syncthing_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?

No guidance whatsoever on when to use this tool versus the many sibling folder/config tools. There are no prerequisites, exclusions, or alternative suggestions.

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