skylight_list_tasks

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

The annotations already declare readOnlyHint=true, and the description merely says 'List', which is consistent. No additional behavioral context is provided—nothing about side effects, permissions, rate limits, or response behavior—so the description adds no transparency value beyond the annotation.

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 compact sentence with a clarifying parenthetical and no filler. Every word contributes to identifying the tool's purpose and scope.

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?

The tool is low-complexity with one parameter and a read-only annotation, so the description is minimally viable. However, there is no output schema, and the description leaves the return structure and the exact role of frameId implicit, which an agent may need for reliable 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?

With 0% schema description coverage, the description must compensate for the bare 'frameId' string. It does add meaning by tying the parameter to 'the frame's task list', but it does not explain requiredness, default behavior, or what happens when frameId is omitted or invalid.

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 a specific verb and resource: 'List task-box items', with a clarifying parenthetical that these are the frame's task list. It is clear enough to distinguish from generic list tools like skylight_list_lists, but it does not explicitly differentiate from close siblings such as skylight_get_list_items or skylight_list_frames.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no mention of when not to use it. The agent must infer from the name and sibling list that this is for tasks specifically.

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