syncthing_needed_files

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering the safety profile. The description adds nothing beyond that - no mention of pagination, syncing states, or what 'needed' files represent - so it contributes zero behavioral context.

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 are technically short, but this is under-specification rather than conciseness - there is no front-loaded statement of purpose or scope to anchor the call.

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 with no output schema, the description is completely inadequate. An agent cannot determine what a 'needed' file is, how pagination works, or how results differ from related sibling tools.

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?

With 5 parameters and 0% schema description coverage, the description carries the full explanatory burden yet says nothing about folder, limit, cursor, fields, or instance. The required 'folder' parameter and the pagination controls (limit/cursor) are entirely undocumented.

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 'Needed files.' merely restates the tool name syncthing_needed_files without a verb, scope, or the folder context implied by the schema's required 'folder' parameter. It does not distinguish this tool from the sibling syncthing_remote_needed_files, leaving the agent unable to tell what 'needed' means or where it applies.

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, when not to, or how it relates to syncthing_remote_needed_files or syncthing_folder_status. The agent is given no routing guidance whatsoever.

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