remarkable_move

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

The description says it 'updates its parent reference', which implies a write operation, consistent with readOnlyHint=false. It also adds mode-level constraints not in annotations. However, it doesn't detail side effects like moving a folder with children, but annotations already cover the write nature.

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 clear sections and front-loaded use case. The XML-like tags add minor noise but do not harm clarity. It is concise without being terse.

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 an output schema exists, the description covers all necessary context: purpose, prerequisites (browse first), parameter details, mode restrictions, and examples. No gaps remain for this mutation 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 fully explains both parameters: document as 'Name or path' and dest_folder as 'destination folder path (use "/" for root)'. Examples show concrete usage.

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 'Move a document or folder to a different location.' This is a specific verb+resource combination, and it distinguishes 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 instructions explicitly tell the agent to use remarkable_browse() first to find the document name. It also specifies that the tool works in cloud and SSH modes but not over USB, and that --read-only disables it.

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