remarkable_status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that it includes 'index statistics when available' and mentions diagnostic info, which is useful extra context beyond the annotations, but it does not detail the exact output or behavior further.

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 well-structured with usecase, instructions, and examples. It is front-loaded with purpose and each section earns its place without redundancy.

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 diagnostic tool with an output schema present, the description covers the purpose, when to use, and a usage example. It does not explain return values, but that is covered by the output schema. Slightly more detail on the 'index statistics' could help, but it is not essential.

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 no description for compact_output (coverage 0%), but the example 'compact_output=True # Omit hints' provides some meaning, indicating it controls whether hints are shown. This is minimal but does add value beyond the schema's bare boolean type.

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 checks connection status and authentication with reMarkable Cloud, using specific verbs and resource. It is distinct from siblings which handle browsing, reading, renaming, etc., so an agent can easily tell them apart.

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?

It explicitly says 'Use this to verify your connection or troubleshoot issues,' giving clear context for when to use. It does not mention alternatives or when not to use, but no overlap exists with siblings, so exclusion is not critical.

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