skylight_clear_list

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

No annotations are provided, so the description carries full responsibility. It states the action (remove all items) but fails to disclose important behavioral traits such as irreversibility, required permissions, or whether the list itself is affected. The description is too sparse for a destructive 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 concise at one sentence. It states the core purpose without extraneous words. However, it sacrifices necessary detail for brevity, making it borderline under-specified. Still, the sentence earns its place by clarifying the function.

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 no annotations, no output schema, and sparse description, the tool definition is incomplete. It lacks information about return values, edge cases (e.g., empty list), parameter dependencies, and side effects. The agent would need to infer or test extensively.

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%, meaning the JSON schema provides no descriptions for the two parameters (listId, frameId). The tool description does not explain their meaning or usage. The agent receives no guidance on what values to provide or how parameters affect the operation.

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 is clear and specific: 'Remove all items from a list.' It uses a strong verb ('Remove') and a specific resource ('all items from a list'). This distinguishes it from sibling tools like skylight_delete_list (which deletes the list itself) and skylight_delete_list_items (which deletes specific items, not all).

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. For instance, it does not clarify when to use skylight_clear_list instead of iterating over skylight_delete_list_items or other methods. No context about prerequisites or conditions is given.

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