move_create_single_cam_take

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

Annotations already signal a mutating, non-idempotent create operation, and the description aligns by saying 'Create'. It adds a useful constraint that files must already be uploaded, but it does not disclose additional side effects or failure modes. No contradiction with annotations.

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 one concise sentence, front-loaded with the action and object, with no filler or redundant restatement of the tool name. Every word earns its place.

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?

The description is minimally sufficient for tool selection and basic invocation, and the schema supplies the nested Source/CameraSettings details. However, it leaves optional-parameter semantics and the distinction from job/multi-cam workflows to be inferred, so it is not fully complete for a tool of this 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 only 25%, so the description should compensate for the undocumented name, expand, and metadata parameters, but it does not. 'Already-uploaded files' only lightly reinforces the file_id provenance already described in the Source 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 uses a specific verb ('Create'), identifies the exact resource ('single-camera take'), and specifies the source precondition ('already-uploaded files'). This clearly distinguishes it from siblings like move_create_multi_cam_take and move_create_single_cam_job.

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 phrase 'from already-uploaded files' implies the tool should be called after files have been uploaded, but it does not explicitly name alternatives or state when not to use it, such as for multi-camera takes or job creation. Usage routing is therefore implied rather than explicit.

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