skylight_move_list_item

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

No annotations are provided, so the description must cover behavioral traits. It only states 'reorder,' implying mutation but lacking details on safety, permissions, or side effects. The agent cannot assess if the operation is destructive or requires special conditions.

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 extremely terse (3 words), which under-specifies the tool's functionality. While short, it fails to convey necessary usage details, making it more 'underspecified' than concise.

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?

Given no output schema, no annotations, low schema coverage, and a single-sentence description, the tool definition is highly incomplete. The agent cannot determine return values, error conditions, or proper invocation context for a tool with 4 parameters.

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's description does not clarify any parameter meanings, such as what 'itemId' or 'listId' represent, nor how to use 'frameId'. The agent must rely solely on the sparse 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 says 'Reorder a list item,' which is a specific verb and resource. It clearly indicates the action of changing order, but does not specify the scope (e.g., within a list) or distinguish from similar actions like setting item sections.

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?

The description provides no guidance on when to use this tool versus siblings, such as 'skylight_set_list_item_section' or 'skylight_update_list_item'. There is no mention of prerequisites or context.

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