sequence.move

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

Annotations indicate the tool is not read-only, not idempotent, and not explicitly destructive, but the description adds no behavioral details about what moving a sequence actually changes. It adds minimal context like "Risk: standard; maturity: L3" and session-policy reminders, but those are not operational behavior such as effects on frames, strips, or scene state.

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 text is short, but this is under-specification rather than concise efficiency. The metadata sentences add no operational value, and the core purpose and parameter guidance are entirely absent.

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 seven parameters, three required, and no behavioral or usage explanation, this description is completely inadequate for an agent to select and invoke the tool correctly. It does not even clarify what "move" means in this context.

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?

With only 43% schema description coverage and required parameters like frameStart and name left undocumented, the description needed to explain parameter meaning but contains none. It does not help an agent understand what values to supply or how they affect the move operation.

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 only restates the tool name as "PartMe Blender Harness command `sequence.move`" and adds risk/maturity metadata. It never states what the tool does—no verb, resource, or effect. This is effectively a tautology with no purpose information.

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 given about when to use this tool versus alternatives, nor any exclusion criteria or prerequisites. The mention that "per-request argument checks and session policy still apply" is generic policy boilerplate, not tool-specific usage guidance.

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