syncthing_device_config

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, but the description adds zero behavioral context beyond them. It does not say whether it reads or mutates config, what it returns, or any instance-scoping behavior, so it contributes nothing to understanding the operation.

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 extremely short, but this is under-specification rather than conciseness - the two-word fragment carries no usable information. There is no structure or front-loaded content to reward.

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 3-parameter tool with no schema descriptions, no output schema, and no annotations covering parameter meaning, the description is completely inadequate. An agent cannot determine what this tool returns or how to shape its arguments.

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 3 parameters (device, fields, instance), so the description must compensate and does not. Nothing explains what 'device' identifies, what 'fields' filters, or what 'instance' selects.

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?

The description 'Device config.' is a bare noun phrase that merely restates the tool name syncthing_device_config. It gives no verb, no scope, and no way to distinguish it from siblings like syncthing_device_defaults, syncthing_devices, 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 whatsoever about when to use this tool, when not to, or which sibling to prefer for related device/config queries. The agent is left to guess entirely.

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