Delete a specific task-box item from your Skylight Calendar to remove completed or outdated tasks.
Delete a task-box item.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| frameId | No |
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 declare destructiveHint=true and readOnlyHint=false, and the description simply says 'Delete' which is consistent. However, it adds no extra behavioral context such as whether deletion is permanent, if it affects associated items, or if special permissions are required. The description provides no value beyond the annotations.
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 sentence with no wasted words, which is concise and front-loaded with the verb. However, it is under-specified for a tool with two undocumented parameters, making it too terse to be genuinely helpful.
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 two parameters, no output schema, and a minimal description. It lacks any explanation of what a 'task-box item' is, how parameters interact, or what the expected outcome is. Given the large set of sibling delete tools, this description is insufficient to guide correct usage.
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 description coverage is 0% and the description does not explain any parameter semantics. It does not mention that 'id' identifies the task or what 'frameId' is used for. With no parameter documentation in the schema and none in the description, an agent cannot correctly construct a valid call without external knowledge.
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 the verb 'Delete' and the resource 'task-box item', which clearly indicates the action and target. However, the term 'task-box item' is somewhat vague—it could refer to a task, a checklist item, or something else—and does not fully clarify what exactly is being deleted, especially given the tool name says 'task'.
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 is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer that it should be used for deleting tasks without any differentiation from sibling delete tools like skylight_delete_meal or skylight_delete_message.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.