syncthing_local_changes

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral detail such as whether results are paginated or folder-scoped, leaving it nearly content-free beyond the read-only signal provided by 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 carry no information; this is under-specification rather than conciseness. There is no front-loaded statement of purpose or scope because there is no content.

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 paginated, folder-scoped read tool with a required parameter, a cursor/limit paging model, and no output schema needs far more than a fragment. Nothing tells the agent what a "local change" is, what fields come back, or how paging works.

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% and the description supplies no parameter meaning at all. Five parameters (limit, cursor, fields, folder, instance) are entirely undocumented, including the required folder argument, so the description does nothing to compensate.

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?

"Local changes." essentially restates the tool name without stating a verb or scope. It does not distinguish this from siblings like syncthing_needed_files or syncthing_folder_status, so an agent cannot tell what this actually retrieves.

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 guidance, no prerequisites, and no reference to any of the 40+ sibling tools. The agent has nothing to route on beyond the name itself.

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