syncthing_system_status

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 nothing further. It does not say what status facets are collected, whether data is live or cached, or what the response contains.

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 two words, but this is under-specification rather than conciseness. Shortness earns no credit when the essential content is absent.

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 zero-required-param, 2-parameter tool with no output schema and 0% parameter coverage, the description supplies no information at all about inputs or behavior. It is wholly inadequate given the surrounding sibling ambiguity.

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 two parameters ('fields' with maxItems 30, and 'instance') are completely undocumented. The description does not mention either parameter, so an agent must guess at the field-name syntax and the meaning of 'instance'.

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?

"System status" merely restates the tool name and tells the agent nothing about what is actually returned or how it differs from siblings like syncthing_overview, syncthing_system_health, syncthing_system_version, or syncthing_system_connections. It is a tautology rather than a specific verb+resource statement.

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 call this tool, when not to, or which sibling to prefer for status-like queries. The dense cluster of sibling 'system_*' tools makes this omission especially costly.

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