Move list items into a named section or clear their current section assignment. Use this tool to organize Skylight lists by grouping items under custom section names.
Move list items into a named section (or clear it).
| Name | Required | Description | Default |
|---|---|---|---|
| listId | Yes | ||
| frameId | No | ||
| section | No | Section name to assign (null/omit to clear the section). | |
| item_ids | Yes | List-item ids to move. |
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.7.1Input schema / properties / item_ids / items / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "number"
- }
-]Input schema / properties / item_ids / items / typeAdded value: +[
+ "string",
+ "number"
+]Input schema / properties / section / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / section / typeAdded value: +[
+ "string",
+ "null"
+]v0.4.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is a mutating, non-destructive operation, so the description needn't restate that. It does add the 'clear it' behavior, but omits details like whether assigning a section overwrites existing assignments or what 'clear it' precisely affects (the item's section or the section's items).
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 short sentence that front-loads the core action and parentheses the secondary mode. It is efficient, though the phrase 'or clear it' is slightly ambiguous and could use a few more words for precision.
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 mutation with no output schema and four parameters, the description is thin. It does not explain the role of frameId, whether the named section must already exist, or how clearing interacts with multiple items. An agent could call it but might misuse the section argument without further context.
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 only 50%: section and item_ids have descriptions, but listId and frameId do not. The tool description does not clarify those parameters or compensate for the gap, so an agent is left guessing what frameId refers to and how listId is formatted.
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 and resource ('Move list items into a named section') and even notes the clearing mode. It implies a distinct operation from siblings like skylight_move_list_item by centering on sections, though it doesn't explicitly name an alternative.
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?
No guidance on when to use this tool versus skylight_move_list_item, skylight_update_list_item, or skylight_clear_list. The intended scenario is implied by the name and description, but there are no explicit conditions, alternatives, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.