syncthing_folder_statistics

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 externally. The description adds nothing beyond them — no indication that results are paged, what the stats represent, or any freshness/aggregation behavior. With annotations reducing the bar, a total absence of added context still warrants a low score.

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 is not conciseness here but under-specification: there is no content to be front-loaded. Nothing is wasted, but nothing is said, so it scores at the level of the tautological 'Process' example rather than earning credit for tight writing.

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 paginated read tool with four undocumented parameters, no output schema, and no annotations explaining return shape, the description is completely inadequate. An agent gets no information about what statistics are returned or how to page through them.

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?

All four parameters (limit, cursor, fields, instance) have 0% schema description coverage, and the description provides no explanation of any of them. Pagination semantics (cursor format, max limit of 1000, field projection, instance scoping) are entirely undocumented, so the description does not compensate for the coverage gap at all.

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 'Folder statistics.' is a noun phrase that merely restates the tool name, with no verb and no statement of what is actually returned or computed. It fails to distinguish this tool from close siblings such as syncthing_device_statistics, syncthing_folder_status, or syncthing_folder_completion, so an agent cannot tell them apart from the text alone.

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 when-to-use, when-not-to-use, or alternative-tool guidance of any kind. The noun 'Folder statistics' at best vaguely implies the domain, but nothing routes the agent between this and the many other syncthing statistics/status tools.

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