get_sleep_movementAccess sleep movement data for a date to identify restless moments and analyze sleep disturbance.
Get movement data during sleep including restless moments.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Date in YYYY-MM-DD format (required) |
Changes observed during successful MCP inspections.
v4.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint and openWorldHint, which cover the main safety behavior. The description adds minimal added behavioral context beyond mentioning 'restless moments,' but it does not contradict or introduce hidden side effects.
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 a single concise sentence, front-loaded with the action and resource. It wastes no words, though adding a usage note would make it even more valuable without harming conciseness.
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?
The tool has only one input parameter and is read-only, so the scope is simple. However, there is no output schema and the description gives limited detail about what the response will contain beyond movement data and restless moments, which leaves some ambiguity.
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 covers 100% of parameters and the required 'date' parameter already has a pattern and description in the schema. The tool description does not explain overlap or usage, but the schema itself handles the semantic burden.
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 uses a specific verb 'Get' and a clear resource: 'movement data during sleep including restless moments.' This differentiates it from broader sleep tools like get_sleep_data and aligns with the tool name without being redundant.
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 does not state when to use this tool versus available alternatives, such as get_sleep_data, heart rate, or stress data tools. It provides no selection criteria, exclusions, or alternative mentions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.