remarkable_markdown_to_pdf

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

Despite annotations only providing readOnlyHint: false, the description fully discloses behavior: it renders specific Markdown elements (headings, lists, tables, etc.), mentions that raw HTML is escaped and images are omitted, details transport-specific behavior (cloud vs SSH vs USB web), and states it requires write mode. 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 clear XML tags (usecase, instructions, parameters, examples) and is appropriately sized for the complexity. Every sentence adds value, from rendering details to transport differences. No fluff.

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 tool's complexity (4 parameters, multiple transports, rendering behavior, and an output schema), the description is comprehensive. It covers transport modes, parameter behaviors, rendering details, and prerequisites (write mode). The presence of examples further enhances completeness.

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?

Schema description coverage is 0%, so the description must compensate—and it does excellently. It explains each parameter with usage notes (e.g., 'Must not be empty' for markdown, defaults, transport-specific behavior like USB web ignoring parent_folder, and defer_restart being SSH-only and forwarded like remarkable_upload). This far exceeds what the schema alone provides.

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 specific verb 'Render Markdown text as a PDF and upload it to the reMarkable tablet,' which precisely identifies the tool's function and distinguishes it from siblings like remarkable_upload (which uploads existing files) and remarkable_image (which handles images). The usecase tag reinforces the purpose.

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 say 'Use this when the user wants notes, reports, summaries, or other Markdown content written back to the tablet without first creating a local file,' providing clear context. It also notes that this tool converts Markdown to PDF, uniquely positioning it among siblings like remarkable_upload which expect pre-made files.

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