remarkable_recent

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

Beyond the readOnlyHint/idempotent annotations, the description adds that previews are served from the local index (no cloud download), the sorting order, the limit behavior (max 50 without preview, 10 with preview), and the REMARKABLE_ROOT_PATH constraint. This gives an agent a solid model of what happens when the tool is invoked.

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 usecase, instructions, parameters, and examples. It is front-loaded with the core purpose and keeps each section tight. No redundant sentences.

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 that an output schema exists, the description doesn't need to explain return values. It covers the main behaviors, constraints, and usage. The only gap is the undocumented compact_output parameter, but overall it's nearly complete for a read-only tool.

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 schema has 0% description coverage, so the description must explain all parameters. It explains limit and include_preview clearly, but omits the compact_output parameter entirely. While examples show usage, the missing parameter prevents a complete understanding.

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 states the specific verb 'Get' and resource 'most recently modified documents', and clarifies sorting behavior. This clearly distinguishes it from siblings like remarkable_search or remarkable_read.

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 instruction 'Use this to quickly find what you were working on recently' provides a clear usage scenario. It also notes the REMARKABLE_ROOT_PATH condition, but does not explicitly mention alternative tools or when not to use this tool.

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