remarkable_upload

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

Beyond the annotation (readOnlyHint=false), the description details transport-specific behavior (cloud, SSH, USB web) and parameter handling, adding significant transparency about limitations and prerequisites (write mode). 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 structurally organized with clear sections (usecase, instructions, parameters, examples). Every sentence adds value, and the most critical info is front-loaded.

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 parameter count and complexity, the description covers use case, supported formats, transport differences, and parameter semantics. An output schema exists, so return values need not be detailed. Slightly missing error handling or success indication, but overall 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?

The input schema has 0% description coverage, so the tool description fully compensates by explaining each parameter's meaning, defaults, and transport-dependent behavior. Examples further clarify 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 the tool uploads PDF or EPUB files to the reMarkable tablet, specifying the resource and action. While it distinguishes from sibling tools implicitly, it does not explicitly differentiate usage scenarios.

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 provides usage context such as supported formats and transport modes, but lacks explicit guidance on when to use this tool versus alternatives (e.g., sibling tools). It does not 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.