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

Annotations already declare this is non-read-only, idempotent, non-destructive, and closed-world. The description adds useful auth context (demos:read, demos:write), but it does not explain side effects such as how other steps are reordered after a move.

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 two short sentences, front-loaded with the core action and positioning modes. The permissions line is compact and no sentence is wasted.

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 simple move operation with no output schema and reasonable annotations, the description covers the key placement options. It still leaves gaps around exactly one placement parameter being required, stepId meaning, and reordering side effects.

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 low (20%), so the description carries extra burden. It helpfully clarifies that toIndex is 0-based and that after/before refer to another step id, but it leaves stepId semantics and the mutual exclusivity of the placement parameters implicit.

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 states a specific verb and resource: moving a step within a guided demo. It clearly describes the positioning options (toIndex, after, before) but does not explicitly distinguish this tool from siblings like update_step or move_scene.

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?

It implies the tool is used when repositioning an existing step and lists the permission requirements. However, it gives no explicit when-to-use guidance versus update_step or move_scene, and no exclusions.

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