remarkable_delete

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable context: item moved to trash (cloud) vs marked deleted (SSH), confirmation requirement, and mode restrictions. This goes well beyond 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?

Structured with usecase, instructions, parameters, and examples. Front-loaded with purpose. Minor redundancy in instructions (e.g., 'DESTRUCTIVE operation' already implied by annotations), but overall efficient.

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?

Covers modal behavior, confirmation, and parameter usage. Since an output schema exists (not shown), return values do not need explanation. No significant gaps given the tool's simplicity.

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 only one parameter 'document' with no description (0% coverage). The description adds meaning: 'Name or path of the document/folder to delete' and provides examples, compensating for the lack of schema description.

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 'Delete a document or folder on the reMarkable tablet.' This directly states the verb and resource, distinguishing it from sibling tools like remarkable_move or remarkable_rename.

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?

Extensive guidance is provided: destructive operation, recovery in cloud vs SSH, mode availability, and confirmation behavior including a flag to skip. However, it does not explicitly state when not to use it (e.g., preferring other tools for listing or reading).

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