syncthing_events

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 covered by structured data. The description adds nothing beyond that, not even the long-poll/timeout semantics implied by the 'timeout' parameter, so it contributes no behavioral context of its own.

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?

A single word is technically terse, but this is under-specification rather than conciseness. Nothing is front-loaded because there is no content 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 six-parameter, open-world, event-streaming tool with no output schema, the description is completely inadequate. An agent cannot determine return shape, pagination behavior, or how the since/limit/timeout parameters interact.

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?

Six parameters (limit, since, events, fields, timeout, instance) are present with 0% schema description coverage, so the description carries the full burden of explaining them. "Events." explains none of them, leaving filters, pagination and the timeout semantics undocumented anywhere.

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 is the single word "Events.", which merely restates the tool name and gives no verb or resource specificity. It does not distinguish this tool from siblings like syncthing_disk_events or syncthing_local_changes, leaving an agent unable to tell what it actually returns.

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 indication of when to use this tool, what alternatives exist, or what conditions select it. With such a large sibling set of event/status tools, this omission is severe.

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