skylight_delete_task

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not say whether deletion is permanent or recoverable, nor what happens to the parent task box, nor what the frameId scoping implies.

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?

A single front-loaded sentence with zero filler and no redundancy. Its brevity is appropriate in form, though the shortness here reflects under-specification rather than economy.

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 destructive mutation with two undocumented parameters, no output schema, and an ambiguous resource name, the description leaves too much unresolved. An agent cannot determine what object it is deleting or what the optional frameId changes.

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%, so the description carries the full burden for `id` and `frameId`, yet it explains neither. 'item' loosely hints that `id` identifies the target, but the optional `frameId` (and why a frame scope would be needed to delete a task) is entirely undocumented.

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?

It states a specific verb ('Delete') and a resource ('task-box item'), so the basic action is clear. However, 'task-box item' is not the vocabulary the sibling set uses (skylight_create_task, skylight_update_task, skylight_list_tasks), so an agent cannot confidently tell whether this deletes a task, a list item, or a frame widget without opening the schema.

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 when-to-use guidance, no prerequisite, and no mention of the sibling tools it competes with (skylight_delete_list_item, skylight_delete_chore, skylight_delete_message). The agent is left to infer applicability purely from the tool name.

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