Set the global reminder cadence by choosing the number of weeks between reminder nudges. Adjust how often Skylight sends reminders to match your preferred schedule.
Set the global reminder cadence (how often Skylight nudges about reminders).
| Name | Required | Description | Default |
|---|---|---|---|
| interval_weeks | Yes | How many weeks between reminder nudges. |
Changes observed during successful MCP inspections.
v1.0.1Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v0.4.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is a write operation but not destructive. The description adds that the effect is 'global' and concerns reminder nudges, which is useful context, but it does not disclose persistence, side effects, or permission requirements.
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 front-loaded sentence with a parenthetical that adds useful clarification. There is no filler or redundant content.
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 one-parameter setter with complete schema coverage and no output schema, the description is sufficient. It names the global scope and the domain effect, and the schema covers the rest.
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 coverage is 100%, and the schema already defines interval_weeks as the number of weeks between nudges. The description does not add constraints, examples, or additional meaning beyond what the schema provides, so baseline 3 is appropriate.
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 states a specific verb ('set') and resource ('global reminder cadence'), then clarifies the meaning with 'how often Skylight nudges about reminders.' This is enough to distinguish it from sibling tools like update_profile or list_nudges.
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?
There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives. The description only restates the operation itself, so an agent receives no help deciding between this and similar settings tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.