remarkable_move

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

The description transparently discloses that the operation is a mutation (readOnlyHint: false aligns with 'move') and explains the internal action: updating parent reference in metadata. It also reveals behavioral details for SSH mode, such as defer_restart skipping xochitl restart and setting 'refresh_pending': true. There is no contradiction with annotations.

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 well-structured with <usecase>, <instructions>, <parameters>, and <examples> sections, each serving a distinct purpose. Every sentence adds value—no fluff or repetition. It efficiently conveys purpose, prerequisites, mode restrictions, parameter details, and usage examples in a compact form.

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?

Given the output schema exists (relieving the description from explaining return values), the description covers all necessary aspects: purpose, prerequisites, mode compatibility, parameter semantics, and behavioral constraints. For a tool with 3 parameters and moderate complexity, this is fully complete.

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?

Input schema coverage is 0%, meaning no parameter descriptions exist in the schema. The description's <parameters> section fully compensates by explaining document ('Name or path'), dest_folder ('use "/" for root'), and defer_restart ('SSH only. Skip the xochitl restart...'). This adds substantial meaning beyond the schema's bare type definitions.

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 explicitly states 'Move a document or folder to a different location', using a specific verb and resource. It also explains the underlying mechanism ('updating its parent reference') and clarifies it works for both documents and folders. This clearly differentiates it from sibling tools like remarkable_rename or remarkable_delete.

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 instructs users to 'Find the document name with remarkable_browse() first', establishing a clear prerequisite. It specifies supported modes (cloud and SSH) and explicitly states unavailability over the USB web interface. It also explains when to use the defer_restart parameter (SSH only). However, it does not explicitly contrast when to use this tool versus alternatives like remarkable_rename, though the context of siblings makes it reasonably clear.

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