skylight_list_lists

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

The readOnlyHint already communicates safety, and the description's 'List' wording is consistent with it. It adds the scoping detail that lists belong to a Skylight frame, but it does not clarify whether frameId may be omitted or what a successful response contains.

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?

One short, front-loaded sentence with no filler or repeated content. It is appropriately sized for the simplicity of the 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?

For a simple read-only list operation with a single parameter, the description is barely adequate, but it leaves gaps: no output format, no explanation of the optional frameId, and no distinction between list containers and their items. The read-only annotation and low complexity keep the missing context manageable.

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?

frameId is a bare string with no schema description (0% coverage), and the description never mentions it directly. The phrase 'on a Skylight frame' weakly implies the parameter identifies the frame, but the description does not compensate for the missing parameter documentation.

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 clear verb ('List') and resource ('all lists on a Skylight frame'), so the operation is identifiable. It does not explicitly contrast with sibling tools like skylight_list_frames or skylight_get_list_items, but the resource name is specific enough to avoid ambiguity.

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 guidance is given about when to choose this tool over the many list- and frame-related siblings. The sentence only describes the action; there are no stated conditions, prerequisites, or alternatives.

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