skylight_get_list_items

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

The readOnlyHint annotation already establishes this as a safe read operation and the description does not contradict it. The description adds scope information ('specific list,' 'Skylight frame') but discloses no additional behavioral traits such as pagination, ordering, or whether frameId disambiguation is required.

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?

A single front-loaded sentence contains only essential information: the verb, resource, scope, and context. There is no filler or repetition of the tool name.

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 getter with no output schema, the description is minimally adequate: it names the returned resource ('items') and the required context (a specific list). It does not address optional frameId semantics, result shape, or pagination, so an agent may have to infer these details.

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%, so the description must compensate, but it only loosely references a 'specific list' and a 'Skylight frame.' It does not explicitly explain that listId identifies the target list or what role the optional frameId plays, leaving a meaningful gap for agent invocation.

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 uses the specific verb 'Get' with the resource 'all items in a specific list,' which clearly defines the operation and distinguishes it from sibling tools like skylight_list_lists (which returns lists) and item-mutation tools such as skylight_update_list_item.

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 implies the tool should be used when retrieving all items for a known list, but it does not explicitly state when to prefer it over alternatives, nor does it mention any conditions or exclusions. It provides implied usage rather than explicit routing.

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