remarkable_search

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: returns summaries from multiple documents, limits on response size, OCR option, and tag filtering, without contradicting 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 uses structured XML tags (usecase, instructions, parameters, examples) for clarity. It is informative and well-organized, though slightly verbose in places but earns its content.

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?

With an output schema present, the description doesn't need to detail return values. It covers limits, parameters, and usage context well. Minor gap: it doesn't specify what 'summaries' entails exactly, but overall adequate.

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 <parameters> section fully describes all 5 parameters, compensating for the 0% schema description coverage. Each parameter's purpose is clear, and examples illustrate usage effectively.

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 it searches across multiple documents and returns matching content. It specifies searching document names and optionally content with grep, distinguishing it from siblings like remarkable_read or remarkable_browse.

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 <usecase> and <instructions> provide context for efficient cross-document search, with explicit limits (max 5 docs, first page ~8000 chars). It lacks explicit when-not-to-use guidance but implies alternatives via sibling list.

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