skylight_delete_list_item

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

Annotations are absent, and the description only says 'Delete'. It does not disclose that the operation is destructive, irreversible, or requires specific permissions. For a mutation tool with no annotation coverage, this is insufficient.

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, which is concise but at the expense of necessary detail. It is not overly verbose, yet it fails to provide sufficient information beyond the basic action.

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?

Given the complexity (3 parameters, no output schema, many sibling tools), the description is incomplete. It lacks parameter explanations, usage context, and behavioral details, making it insufficient for correct tool selection and 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%, and the description adds no meaning to the three parameters (itemId, listId, frameId). It does not explain their roles or relationships, leaving the agent without essential context.

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?

Description states 'Delete a list item from a Skylight frame' with a specific verb and resource. However, sibling tools like 'skylight_delete_list_items' (batch delete) and 'skylight_delete_list' are not differentiated, so it misses the top score for distinguishing from alternatives.

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 usage guidance is provided. There is no mention of when to use this tool over similar siblings (e.g., skylight_delete_list_items, skylight_move_list_item). The description implicitly assumes delete individual item but lacks explicit context or exclusions.

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