remarkable_recent

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

Annotations already declare readOnlyHint and idempotentHint, indicating safety. The description adds valuable behavioral details: documents sorted by modification date (newest first), optional preview of ~200 chars, and path restriction if REMARKABLE_ROOT_PATH is configured. No contradictions 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 using XML tags (usecase, instructions, parameters, examples) and is front-loaded with the primary purpose. Every sentence is informative and necessary. No wasted text.

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?

For a simple read tool with two parameters, the description covers all necessary aspects: purpose, usage, behavioral notes, parameter details, and examples. Output schema exists, so return values are already documented. The description is fully adequate for agent invocation.

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 compensates by explaining both parameters: limit (default 10, max 50 without preview, 10 with preview) and include_preview (default False, includes ~200 chars). This adds meaningful guidance beyond the schema's type/default values.

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: 'Get your most recently modified documents.' It uses a specific verb ('get') and resource ('recently modified documents'), and distinguishes itself from siblings like 'remarkable_search' (search by query) and 'remarkable_browse' (browse folders) by focusing on recency.

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 usage context: 'Use this to quickly find what you were working on recently.' While it does not explicitly state when not to use or mention alternatives, the context is sufficient for an agent to understand appropriate use cases.

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