remarkable_render_document

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

No annotations are present, so the description carries the full burden. It discloses the return values and the fact that it renders all pages to a single PDF, but lacks details on side effects, storage location, or error handling. Acceptable for a simple render operation.

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?

Two concise sentences. The first states the primary function, the second clarifies the wrapper relationship and return values. No unnecessary words.

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?

The tool is simple (one parameter), has an output schema (though not shown), and the description mentions what will be returned. It doesn't mention that doc_id should come from list_documents, but that's a minor omission. Overall sufficiently complete for the tool's complexity.

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 single parameter doc_id is self-explanatory and its role is implied by the description. Schema coverage is 0%, but with only one obvious parameter, the description doesn't need to add much. Still, it doesn't explicitly define doc_id, so it doesn't fully compensate for the lack of schema descriptions.

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 action: 'Render all pages of a reMarkable document to a single PDF.' It also distinguishes this tool from sibling render_pages by explicitly calling it a convenience wrapper equivalent to render_pages with no selection args.

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 implies when to use this tool: when you need all pages rendered, as opposed to selecting specific pages via render_pages. It doesn't explicitly say 'use render_pages for selected pages,' but the wrapper equivalence makes that clear enough.

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