remarkable_upload

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

Annotations show readOnlyHint=false and destructiveHint=false, so the description already knows it's a non-destructive write. The description adds transparency about format restrictions and destination behavior, which complements the annotations well.

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-organized into usecase, instructions, parameters, and examples. Every sentence adds value, and the length is appropriate.

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 formats, destination, prerequisites, and examples. Lacks mention of return value or success status, but given the output schema exists (though not shown), this is a minor gap.

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 adds full value: explains file_path as 'Absolute path to local PDF or EPUB file' and destination as 'Folder path on tablet (default: "/" for root)'. This is essential for correct invocation.

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's purpose: 'Upload a PDF or EPUB file to your reMarkable tablet.' It uses a specific verb-resource combination and is distinguishable from siblings like remarkable_read 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?

Provides explicit instructions on when to use (uploading local files), format restrictions (only PDF/EPUB), and prerequisite actions (use remarkable_mkdir if destination folder doesn't exist). Includes multiple examples.

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