remarkable_list_documents

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

With no annotations, the description carries the full burden of behavioral disclosure. It specifies the data source ('local cache'), the case-insensitive substring filtering behavior, and the return fields. This goes beyond the schema and conveys a read-only listing operation, though it does not explicitly state that it is safe or non-mutating.

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 three short sentences: purpose, filter behavior, and return fields. No wasted words, information is front-loaded and easy to scan. Every sentence earns its place.

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 list tool with one optional parameter and an output schema, the description covers all essential aspects: what is listed, where from, how to filter, and what is returned. The output schema likely documents return types, so no further detail is needed. The description is complete for a task of this complexity.

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 one parameter ('search') with no description, so the description must compensate. It fully explains the parameter: optional, case-insensitive substring filter on document names. This adds complete meaning beyond the bare schema definition.

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 'List documents in the reMarkable local cache' with a specific verb and resource. It distinguishes this list operation from sibling tools like remarkable_get_document_info (which likely retrieves a single document) and render tools. The scope is unambiguous.

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 implies usage for listing documents but provides no explicit guidance on when to use this tool versus alternatives. It does not mention when to prefer get_document_info or render tools, nor does it state any exclusions or prerequisites. The optional filter hints at use cases but not in a prescriptive way.

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