skylight_move_list_item

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

Annotations already declare it as non-read-only and non-destructive, so the agent knows it's a mutating operation. The description 'reorder' adds minimal context beyond implying a change in position. It does not disclose side effects like shifting other items, nor whether the operation is reversible. With annotations covering the safety profile, this is acceptable but adds little extra behavioral detail.

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 short sentence with zero filler, making it concise and front-loaded. It efficiently states the core operation. However, it may be too sparse given the tool's parameter count, but for conciseness it scores well as it contains no unnecessary words.

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 4 parameters, 2 required, low schema coverage, and no output schema, the description is incomplete. It does not explain the positional mechanics (e.g., how afterItemId controls placement), whether the item must already exist, or what happens to the list ordering. An agent would need to infer behavior from the schema and name, missing critical context for correct 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?

Schema description coverage is only 25% (only afterItemId has a description). The tool description does not compensate for the undocumented listId, itemId, or frameId. While their names suggest obvious roles, the agent receives no explicit explanation of what 'listId' refers to or how 'frameId' might be optional. The description adds no parameter semantics beyond the schema.

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 'Reorder a list item' clearly states the verb and resource, which is unambiguous and distinct from sibling tools like add/update/delete. It focuses on the reordering operation, not moving between lists or other actions. No alternative tool handles this specific operation, so differentiation is not needed, but it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool vs. alternatives. There is no mention of prerequisites, such as the item existing in the list, or when to use this over skylight_set_list_item_section (which also affects ordering indirectly). It does not state that this is exclusively for reordering within the same list, nor any exclusions.

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