remarkable_move

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

Discloses it updates parent reference (mutation). Warns about mode dependencies (not available over USB). No annotations beyond readOnlyHint=false, so description adds useful behavioral context. Could mention permissions or behavior if destination exists.

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?

Structured into usecase, instructions, parameters, and examples. Each section adds value. Slightly verbose due to XML tags, but concise in content. Examples are helpful.

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?

Covers prerequisites, modes, parameter details, and examples. Output schema exists but not shown; description adequately explains behavior for a move operation. No missing critical information.

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?

Despite 0% schema coverage, description adds full parameter meaning: document as 'name or path' and dest_folder as 'destination folder path (use / for root)'. Examples clarify usage. Compensates for schema lack completely.

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?

Clearly states it moves a document or folder to a different location. Verb 'move' and resource 'document or folder' are specific. Distinguishes from siblings like rename or 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?

Advises to first find the document with remarkable_browse(). Notes availability in cloud/SSH modes but not over USB. Implies usage context but lacks explicit alternatives or when-not-to-use scenarios.

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