skylight_update_list_item

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only restates the mutation ('update') without indicating whether updates are partial or full, whether unspecified fields are preserved, or what side effects occur. The schema's checked and section descriptions hint at behavior, but the description itself adds no behavioral context.

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?

The description is a single succinct sentence with the action front-loaded and no filler, which is structurally clean. However, it is undersized for a six-parameter operation and misses opportunities to add field semantics or usage guidance without becoming bloated.

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?

With six parameters, no output schema, no annotations, and a large set of closely related sibling tools, a one-sentence description is inadequate. It leaves unclear how updates behave, which fields are relevant, how IDs relate, and when to pick this tool over similar list-item operations. The low schema coverage amplifies these gaps.

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 33%, and the description does not compensate for the undocumented parameters. It does not explain label, listId, itemId, or frameId, nor does it clarify which fields are optional and updatable. Only checked and section carry schema-level descriptions, so four of six parameters remain semantically bare.

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 ('update') and resource ('list item') and locates the operation on a Skylight frame, making the core action clear and distinguishing it from higher-level tools like skylight_update_list. However, it does not say which attributes are updatable or what distinguishes it from item-level siblings like move or set-section operations.

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 closely related siblings such as skylight_set_list_item_section, skylight_move_list_item, or skylight_add_list_item. The description provides no context, exclusions, or alternatives, leaving the agent to infer selection from names alone.

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