vegas_motion

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

With no annotations, the description carries the full behavioral burden, and it largely fails. 'Change' implies mutation and the set_/clear_ actions are presumably destructive, but nothing states reversibility, required permissions, confirmation behavior, or what 'guarded' actually means — the one unusual term is left undefined and adds ambiguity rather than clarity.

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 clean, front-loaded sentence with no filler, which is maximally concise. However, for a six-action dispatch tool with an opaque nested params object, one sentence is undersized rather than efficiently scoped.

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?

No annotations, no output schema, six enum actions, and an undocumented nested params object. The description does not explain return values (which it would need to, given no output schema), the params structure, or the meaning of 'guarded' — significant gaps against this tool's complexity.

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 0% and the 'params' object is an unconstrained nested object with additionalProperties: {} and no documented shape. The description names the event vs. track distinction, which loosely maps to the enum, but gives no hint about the per-action parameter payload the agent must construct.

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 pair and resource: 'Inspect and change ... motion keyframes', scoped to event pan/crop motion and video-track motion. An agent can tell this is the motion/keyframe domain rather than project, timeline, or render. It does not name a sibling, but the domain is distinctive enough to be recognizable.

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 when-to-use or when-not-to-use guidance is given, and no alternative tool is named. The description does not clarify when to reach for vegas_motion versus vegas_effects or vegas_timeline, so action selection and tool selection are both left to inference.

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