remarkable_render_pages

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains selection behavior, gives a concrete example, and lists return values. However, it does not mention side effects such as creating files on disk, whether previous renders are overwritten, or if cleanup via 'remarkable_cleanup_renders' is needed. This is a meaningful gap for a render tool with file output.

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 four compact sentences: purpose, priority rule, example, and return values. Every sentence earns its place, and the most important information is front-loaded. There is no redundancy or unnecessary detail.

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 description is adequate for a moderately complex tool with one required param and an output schema. It covers selection priority, example behavior, and return values. The main omissions are index base, potential side effects/cleanup, and how it differs from the full-document sibling, but overall it gives the agent enough to invoke correctly.

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 for the input schema. It clarifies the meaning and precedence of 'page_indices', 'last_n', 'first_n' and the 'all pages' fallback, using a concrete example. However, it leaves some semantics implicit (e.g., whether indices are zero-based, bounds behavior, doc_id role) and does not fully describe all parameter formats.

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 opens with a specific verb and resource: 'Render selected pages of a reMarkable document to a single PDF.' The phrase 'selected pages' distinguishes it from the sibling tool 'remarkable_render_document,' which presumably renders the full document. The purpose is immediately clear and non-tautological.

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 clear intra-tool guidance on parameter precedence ('Priority: page_indices > last_n > first_n > all pages') and a concrete example. However, it does not explicitly state when to use this tool versus alternatives like 'remarkable_render_document' or 'remarkable_cleanup_renders.' The usage context is implied by the 'selected pages' framing but not explicitly contrasted.

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