skylight_get_list_items

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the scope note that it returns ALL items, without stating pagination behavior, what an item looks like, or what happens for an unknown list/frame. With annotations carrying the safety burden, this is adequate but thin.

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 with no filler; the action and resource come first. It is efficiently sized, though its brevity is partly a symptom of missing detail rather than disciplined trimming.

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 two-parameter read tool with annotations and no output schema, the description is minimally sufficient to identify the operation. It falls short on the frameId/listId relationship and any return-shape expectations, which matters because the schema documents neither parameter.

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 coverage is 0%, so the description must compensate and it does not: it never explains that listId identifies the target list, that frameId is optional, or how the two interact ('a Skylight frame' hints at frameId but gives no rules). The only real hint is the phrase 'on a Skylight frame'.

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 gives a specific verb+resource ('get all items') and scopes it to 'a specific list on a Skylight frame', which distinguishes it from skylight_list_lists (which enumerates lists) and the list-item mutation tools (add/update/delete/clear). It does not, however, explicitly contrast itself with those siblings, so the distinction must be inferred.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., needing a valid list), and no reference to alternatives such as skylight_list_lists for discovering list IDs. The agent is left to infer the whole usage context.

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