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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is known. The description adds essentially nothing beyond that: it does not say what happens to the shots displaced by the move, whether positions shift or are swapped, or whether the move can be undone, which is the key context for a destructive reorder.

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 sentence with the action and target front-loaded and no filler. It is efficient, though its terseness contributes to the missing behavioral detail noted elsewhere.

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 a fully described 3-parameter schema, existing output schema and annotations, the definition is largely self-sufficient for invocation. What it lacks is the behavior of a destructive reorder — displacement of other shots and any confirmation prerequisite — which matters given destructiveHint=true.

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 100%, so all three parameters (photoId, position, listingId) are already documented, including the 1-based convention and the 'shot 3' play-position alias. The description's '1-based position' merely restates the schema, adding no new meaning; baseline 3 applies.

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?

States a specific verb and resource ('Move one shot') plus the target semantics ('to a 1-based position in the video'), so the agent can tell this is a reorder operation. It does not name or contrast with adjacent shot-mutation siblings such as frame_shot or set_shot_length, but the purpose itself is unambiguous.

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 explicit when-to-use, when-not-to-use, or alternative guidance. The agent must infer from the verb that this is for reordering existing shots rather than adding or trimming them, and nothing says whether a confirmation step (e.g. confirm_action) is expected before a destructive move.

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