remarkable_recent

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds behavioral details: documents are sorted newest-first, optional text preview (first ~200 chars), and the REMARKABLE_ROOT_PATH constraint. These go beyond the annotations, though the description could mention pagination or result truncation limits.

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 uses structured tags (<usecase>, <instructions>, <parameters>, <examples>) for clarity. Every sentence is informative and front-loaded with the use case. It is concise with no wasted 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?

Given the tool's simplicity (2 optional parameters, output schema exists), the description covers all essential aspects: use case, behavior, parameter details, examples, and the REMARKABLE_ROOT_PATH note. It is complete for an AI agent to select and invoke the tool 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?

The input schema has 0% description coverage, so the description fully compensates by clearly explaining each parameter: limit (default, max constraints) and include_preview (preview length). This adds significant semantic value beyond the schema's raw definitions.

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 specifies the verb (get) and resource (recent documents) and distinguishes the tool from siblings through its focus on recentness and modification date ordering.

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 explicit guidance on when to use the tool ('Use this to quickly find what you were working on recently') and includes instructions on parameters and environment variable behavior. However, it does not explicitly mention when not to use it or suggest alternative tools for other scenarios.

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