remarkable_mkdir

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

Despite readOnlyHint=false annotation, description adds context about sync behavior, mode availability, and restart requirement in SSH mode. No contradiction.

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 clear tags (usecase, instructions, parameters, examples). Each sentence is valuable, no redundancy. Front-loaded with purpose.

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 all essential aspects: purpose, modes, parameters, examples. Output schema exists, so return value explanation is unnecessary. Complete for a simple creation 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?

Schema has 0% description coverage, but the <parameters> section explains folder_name and parent with defaults and examples, adding significant meaning beyond schema titles.

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?

Clearly states 'Create a new folder on the reMarkable tablet.' with a usecase tag. Differentiates from siblings like remarkable_delete and remarkable_rename by focusing on creation.

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?

Specifies modes (cloud/SSH, not USB web interface) and mentions that in SSH mode the folder appears after xochitl restarts. Provides examples but does not explicitly compare to sibling tools.

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