skylight_delete_list

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is fully captured. The description adds no additional behavioral context, such as whether deletion is irreversible, whether list items are also deleted, or whether frameId affects the operation.

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 very short and free of fluff, which is good for conciseness. However, it is under-specified: a single generic sentence carries no structural information about the parameters or the operation's scope, so the brevity comes at the cost of usefulness.

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?

With two parameters, no output schema, and no parameter descriptions, this minimal definition leaves important gaps. The agent cannot tell why frameId exists, whether deletion requires it, or what side effects occur, so the context is not complete enough for reliable invocation.

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%: neither listId nor frameId has a description. The description 'Delete a Skylight list' adds no meaning about what listId identifies or when frameId is needed, leaving all parameter semantics unexplained.

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 'Delete a Skylight list' states a specific verb and resource, making the core purpose unambiguous. However, it does not distinguish itself from closely related sibling tools like skylight_clear_list or skylight_delete_list_items, so the agent must infer the difference from the name alone.

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 provides no guidance on when to use this tool versus alternatives such as skylight_clear_list for clearing list contents or skylight_delete_list_items for removing individual items. There are no conditions, exclusions, or alternative suggestions.

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