syncthing_file_versions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered, but the description adds nothing on top: no pagination behavior, no auth/instance requirements, no note on what version set is returned. It contributes zero behavioral context beyond the structured fields.

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 technically brief, but this is under-specification rather than conciseness; there is no front-loaded verb or scope sentence that earns its place. Mirrors the calibration's 'Process' case.

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 5-parameter, paginated, folder-scoped query tool with no output schema and no parameter documentation, the description is wholly inadequate. An agent cannot form a correct call from it.

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 5 parameters (folder, limit, cursor, fields, instance). The short description mentions no parameter at all, so an agent gets no meaning for required 'folder', the cursor/limit paging contract, or the 'fields' projection list.

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?

"File versions." is a noun phrase that essentially restates the tool name rather than stating an action. It signals the resource (file version history) but gives no verb, no scope, and no way to distinguish it from siblings like syncthing_file_metadata or syncthing_folder_browse.

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 use this tool, when not to, or which sibling to prefer. With 37 sibling tools in the family, the absence of routing information is a serious gap.

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