Manage remio sync folders

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

The description discloses important behavioral traits beyond the minimal annotations: changes require explicit confirmation, and removing a folder preserves already-created notes. This adds meaningful safety context that the readOnlyHint and destructiveHint booleans do not convey, though it doesn't cover all actions (e.g., pause/resume effects).

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?

The description is two sentences, front-loaded with the core purpose, and every clause adds value. It avoids repetition or filler.

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?

The tool has multiple actions and no output schema, yet the description only elaborates on 'remove' and the confirmation requirement. It does not explain what happens with 'add', 'pause', 'resume', or what the result of 'list' looks like. This is incomplete for a multi-action tool.

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 0% schema description coverage, the description must compensate, but it only indirectly explains the 'action' and 'confirm' parameters. The 'path' parameter is completely unexplained, and the enum actions like 'pause' and 'resume' are not elaborated. This falls short for a tool with few parameters.

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 clearly states the tool 'lists or changes folders that remio indexes' with a specific verb and resource. While it doesn't explicitly differentiate from sibling tools, the focus on sync folder management is distinct from other remio tools like remio_notes or remio_collections.

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?

The description implies when to use the tool: to manage sync folders. It provides some contextual guidance by noting that changes require confirmation, but it does not explicitly contrast with alternative tools or state when not to use it.

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