skylight_delete_list_items

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

With no annotations, the description must carry the full burden of behavioral disclosure. It reveals the operation is destructive (delete) but does not mention permanence, side effects, or the role of the optional frameId parameter. For a mutation tool this is a meaningful gap.

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 zero filler. Every word contributes meaning, and it is appropriately brief for a simple bulk-delete operation.

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?

Without an output schema or annotations, the description is too sparse to fully specify invocation. It omits the meaning of listId and frameId, provides no usage boundaries relative to sibling tools, and does not describe the result of a successful bulk delete.

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 only 33% (only item_ids has a description). The description adds no clarification for listId or frameId and only weakly corresponds to item_ids via 'list items'. It does not compensate for the low schema coverage.

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 ('Bulk-delete') and resource ('list items'), clearly identifying a batch deletion operation. 'Bulk' and 'specific' implicitly distinguish it from the singular sibling skylight_delete_list_item and the clear-all sibling skylight_clear_list, though it does not name them explicitly.

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 term 'Bulk' implies this tool should be used when deleting multiple specific list items, but there is no explicit guidance on when to choose it over skylight_delete_list_item for a single item or skylight_clear_list for all items. The usage context is only implied, not stated.

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