skylight_set_list_item_section

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

No annotations are present, so the description carries the full burden of disclosing behavior. It indicates a mutating operation and the ability to clear a section, but it does not disclose side effects, authorization requirements, reversibility, or what happens to unspecified list items. This is comparable to a generic mutation description that leaves important behavioral context implicit.

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 that states the primary action and the notable null-clear behavior with no filler. It is as concise as possible while conveying the essential 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?

For a mutation tool with four parameters, no annotations, and no output schema, the description should provide more context to support correct invocation. It omits when to use the tool, what frameId means, and what the operational effects are beyond the basic move/clear action, leaving an agent under-informed.

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 only 50%, and the description does not compensate for the undocumented listId and frameId parameters. It loosely maps to 'section' and 'list items,' but adds little meaning beyond what the schema already states for section and item_ids. The required listId parameter has no semantic explanation in either the schema or the description.

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 clear verb and resource: 'Move list items into a named section,' which conveys the core operation. It also adds the 'clear it' alternative, but it does not explicitly distinguish itself from the sibling tool skylight_move_list_item, leaving a potential 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?

There is no guidance on when to use this tool versus alternatives like skylight_move_list_item or skylight_update_list_item. The description states what it does but not the conditions or intent that should lead an agent to select it.

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